How to work with certificates in Java keystore
The following article is for users using the Apache Tomcat server, signing Java applications, and working with Java keystrokes in general.
Create a keystore and key pair
This command creates a new keystore and key pair that you use to create the certificate request.
keytool -genkey -alias test -keyalg RSA -keystore test.jks -keysize 3072
You will then be prompted to enter the keystore password and specify it. The entered data will match those in the CSR:
What is your first and last name?
[Unknown]: Test Test
What is the name of your organizational unit?
What is the name of your organization?
[Unknown]: Test corp.
What is the name of your City or Locality?
[Unknown]: Some City
What is the name of your State or Province?
[Unknown]: Some State
What is the two-letter country code for this unit?
Is CN=Test Test, OU=Unit, O=Test corp., L=Some City, ST=Some State, C=US correct?
Create a CSR
To create a CSR, use the following command:
keytool -certreq -alias test -keystore test.jks -file test.csr
You entered the requester details when you created the key pair in the previous step, so the keytool no longer asks for them.
The -file test.csr parameter is used to output the CSR to a file. If you omit it, the CSR will be displayed in the terminal and you can copy it directly to our order. Then just wait for the certificate to be issued.
Import issued certificate into keystore
You will receive an issued certificate from SSLmarket by e-mail and must be sent to the keystore.
Keystore requires that the certificate be trusted and the issuing authority is already present in the keystore when importing certificates. This means that certificates are imported in "reverse order" - from root to server.
keytool -import -trustcacerts -alias test -file test.txt -keystore test.jks
Error: Failed to establish chain from reply
The previously requested CA import to the keystore causes a frequent keytool error: java.lang.Exception: Failed to establish chain from reply error. An error means that there is no issuing CA/intermediate certificate in the keystore.
To fix this:
1) import in reverse order - CA certificates first:
keytool -import -trustcacerts -alias root -file intermediate.crt -keystore test.jks
2) or by importing the certificate in PKCS#7 (P7B) format. Convert the linux_cert+ca.pem file you received from SSLmarket to P7B with the following command:
openssl crl2pkcs7 -nocrl -certfile-linux_cert+ca.pem -out linux_cert+ca.p7band then import this file into the keystore:
keytool -import -trustcacerts -alias test -file linux_cert+ca.p7b -keystore test.jksThe result Certificate reply was installed in keystore means successful import, while error Public keys in reply and keystore do not match means that there is no certificate for the domain in the P7B file (server, endpoint), but only intermediate.
3) eventually by importing a certificate in PKCS # 12 (PFX) format in which everything is together:
keytool -importkeystore -srckeystore pkcs12file.p11 -srcstoretype pkcs12 -destkeystore test.jks -deststoretype JKSImporting with PKCS#12 is the fastest, but if you were doing CSR directly in the keystore, it is unnecessary (requires its export).
If you don't want to work with a keystore using a command line or terminal, you can use one of the few GUI tools.
Both of these programs can create or open a keystore file, create a CSR, and import a reissued certificate (response from a CA). The procedure is the same as that for the terminal above; the difference is the graphical environment in which you can do it.
Portecle is a free Java program that allows you to manage a keystore in a graphical environment. You can run it on different platforms (Linux, MacOS, Windows).
KeyStore Explorer works similarly to the previous program and is also cross-platform.
However, the logic of both programs is similar to the original keystore; as a result, it may not save you much.