Replies: 3 comments
-
It looks like Jsign can't access the hardware token. Are you sure the build is run in the same environment and not inside a container lacking access to the token? |
Beta Was this translation helpful? Give feedback.
0 replies
-
What Java version? It might be an upstream bug. corretto/corretto-8#306 |
Beta Was this translation helpful? Give feedback.
0 replies
-
I don't think it'is related to this issue, this looks more like a bad SunPKCS11 configuration. @mrshorten could you try again with the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am attempting to automate Code signing from our bamboo server. Everything seems to work well when remotely logged into the machine using this command:
java -jar C:\Users\USER\jsign-4.1.jar --keystore C:\Users\USER\eToken.cfg --alias "ALIAS" --storetype PKCS11 --storepass PASSWORD --alg SHA-256 --tsaurl http://timestamp.digicert.com --tsmode RFC3161 FILE_TO_SIGN
However when running that same command as part of a build task i get the following error. The bamboo service is running as the same user that i remotely logged into. Any thoughts would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions