Replies: 1 comment 2 replies
-
With Java 11+ some modules have to be added to the module path to avoid a runtime error.
With the Azure CLI:
You don't run Jsign directly to sign a jar file. You run jarsigner and specify the Jsign provider to access the keystore. |
Beta Was this translation helpful? Give feedback.
2 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.
-
Hi, I'm currently trying to test viability of using AKV to store our Java code signing certificate.
I currently use a local certificate, and use the ant signjar task for jar signing.
When trying to test a self signed certificate in AKV (before purchasing a real one)
I've come across various issues with setting classpath etc (as I need to use Java 8 and Java 21)
I was led to this tool, which seems it could be what I need.
Is there a simple guide to using this tool with AKV to sign jar files?
I've seen this example:
jarsigner -J-cp -Jjsign.jar -J--add-modules -Jjava.sql \ -providerClass net.jsign.jca.JsignJcaProvider \ -providerArg <vault-name> \ -keystore NONE \ -storetype AZUREKEYVAULT \ -storepass <api-access-token> \ application.jar <key-name>What is the significance of the "java.sql" argument?
How do I generate an API access token?
I've tried running this with some arguments missing hoping to get some useful error messages but it seems to indicate it won't work with jar files. And infact jar files are not listed on the supported file types list.
java -jar repository\jsign-7.4.jar --storetype AZUREKEYVAULT myApplication.jar jsign: Unsupported file: myApplication.jarThanks for any advice on this.
Beta Was this translation helpful? Give feedback.
All reactions