Keytool Error Java.Lang.Exception Input Not An X509 Certificate (Resolved)

The "keytool error java.lang.exception: input not an X.509 certificate" error occurs when you are trying to import a certificate into the keystore using the keytool command and the certificate file you are trying to import is not in the X.509 format.

To fix this error, you can follow these steps:

  1. Verify that the certificate file you are trying to import is in the X.509 format. You can use a text editor to open the file and check the format.
  2. If the certificate file is not in the X.509 format, you will need to convert it. You can use the openssl command to convert the certificate file to the X.509 format. The command would look something like this:
openssl x509 -inform der -in certificate.cer -out certificate.pem

3.Once you have the certificate file in the X.509 format, you can import it into the keystore using the keytool command. The command would look something like this:

keytool -import -alias myalias -keystore mykeystore.jks -file certificate.pem

4.When prompted, enter the keystore password and then confirm the import.

5.Verify the certificate has been imported by executing the command:

keytool -list -v -keystore mykeystore.jks

6. After you have imported the certificate into the keystore, you will need to configure your application to use the keystore. This typically involves setting the appropriate system properties or environment variables.

For example, to configure a Java application to use the keystore, you would set the following system property:

-Djavax.net.ssl.keyStore=path/to/mykeystore.jks

7. You may also need to configure the truststore for your application. This is typically done in a similar way to configuring the keystore.

For example, to configure a Java application to use a truststore, you would set the following system property:

-Djavax.net.ssl.trustStore=path/to/mytruststore.jks

8. Once you have configured the keystore and truststore for your application, you should test your application to make sure it is working correctly.

9. If you are still facing issues, check the keystore and truststore for correctness by listing the certificates in them and check the ownership, if the certificate imported is the one you intended to import.

10. If you continue to have issues, it may be necessary to consult the documentation for your application or the experts of your organization, to troubleshoot the problem further.

Product Support Portal | SmartBear Software

Frequently Asked Questions About The Error

What causes the "keytool error java.lang.exception: input not an X.509 certificate" error?

This error occurs when the certificate file that is being imported into the keystore using the keytool command is not in the X.509 format.

How can I check if a certificate file is in the X.509 format?

You can open the certificate file using a text editor and check the format. The file should start with "-----BEGIN CERTIFICATE-----" and end with "-----END CERTIFICATE-----".

What is the openssl command to convert a certificate file to the X.509 format?

A: The openssl command to convert a certificate file to the X.509 format is:

openssl x509 -inform der -in certificate.cer -out certificate.pem

Q: How do I import a certificate into the keystore using the keytool command?

The command to import a certificate into the keystore using the keytool command is:

keytool -import -alias myalias -keystore mykeystore.jks -file certificate.pem

How do I configure my application to use the keystore?

To configure a Java application to use the keystore, you need to set the following system property:

-Djavax.net.ssl.keyStore=path/to/mykeystore.jks

How do I configure my application to use the truststore?

To configure a Java application to use the truststore, you need to set the following system property:

-Djavax.net.ssl.trustStore=path/to/mytruststore.jks

How can I check if my keystore and truststore are correctly configured?

You can check the keystore and truststore by listing the certificates in them and check the ownership, if the certificate imported is the one you intended to import.

Great! You’ve successfully signed up.

Welcome back! You've successfully signed in.

You've successfully subscribed to Lxadm.com.

Success! Check your email for magic link to sign-in.

Success! Your billing info has been updated.

Your billing was not updated.