I'm submitting a…

• bug report
• feature request
• other

We'd like to use jsign with SSL.com's eSigner, and jsign supports this from version 4.1 on (https://github.com/ebourg/jsign/releases/tag/4.1). I saw that the relevant params are already passed to jsign unaltered (except for storetype=PKCS11).

What is the motivation / use case for changing the behavior?

MS Authenticode requires USB-Tokens for Key-Storage from now on. An alternative is string the Key at a external Service that allows access to the signing process via API. SSL.com offers an API that jsign supports.

Other information (e.g. related issues, suggestions how to fix, links for us to have context)

The API of jsign might have changed since the versin curently used... if this is more than a simple change in the pom.xml then i'll work on a pull request.