Page 3
BlackVault HSM Java Configuration Guide USA, FCC This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation.
BlackVaultSetupCD’s Configuration folder. The default provided nss.cfg file is set up for the BlackVault HSM User on slot 1. Only one user at a time can use Java utilities and keytool. To give access to a user that is not on slot 1, the nss.cfg file will have to be edited before completing the steps below.
2.2. Linux If you are using machine with a Linux operating system, follow the instructions in this section to properly set up Java with a BlackVault HSM. 2.2.1. Java 8 1. Install Java 8 2.
The path to the nss.cfg file will be /usr/lib/jvm/(java directory for desired version)/conf/security/nss.cfg 2.3. Windows If you are using machine with a Windows operating system, follow the instructions in this section to properly set up Java with a BlackVault HSM. 2.3.1. Java 8 1. Install Java 8.
BlackVault HSM Java Configuration Guide security.provider.11=sun.security.pkcs11.SunPKCS11 path to nss.cfg file i. The path to the nss.cfg file will be:C:\\Program Files\\Java\\(JRE or JDK folder)\\lib\\security\\nss.cfg 2.3.2. Java 11/14 1. Follow steps 1-4 of Java 8 install for desired Java version (11 or 14).
To do code signing per industry best practices, along with storing the key inside a secure BlackVault HSM, a code signing certificate associated with the key is required. For the Java environment, if all the prerequisites have been competed (Java configured correctly, and PKCS#11 library installed) complete the following steps: 1.
3.2. Eclipse IDE The BlackVault HSM’s integration with Eclipse involves a straightforward modification of the Apache ant build.xml build file. In the following section, the highlighted portions of text are specific to your build environment and project. Refer to your eclipse-workspace for correct paths and names.
If jar verification is unsuccessful, output will display jar is unsigned 3.3. Android Studio The BlackVault HSM’s integration with Android Studio involves a straightforward modification of the build.gradle file. In the following section, highlighted portions of text are unique to the build machine and project.
BlackVault HSM Java Configuration Guide task sign(type: Exec) { executable ”jarsigner” args”-keystore”,”NONE”,”-storetype”,”PKCS11”,”-storepass”,”2222”,\ ”C:\\User\\user\\AndroidStudioProjects\\MyApp\\app\\build\\outputs\\apk\\re lease\\app-release-unsigned.apk”,\ ”2048key” 6. From the tool bar, select app then Edit Configurations... in the drop-down menu. 7. Select + (top left) then Gradle. 8. In the Gradle Project: section, enter: a.
Need help?
Do you have a question about the BlackVault HSM and is the answer not in the manual?
Questions and answers