Input Not An X.509 Certificate


When one of the following circumstances is met, this error occurs:
During the import command, the wrong alias was supplied.
When attempting to import the certificate, no alias was supplied.
During the import operation, the wrong Keystore file was utilized.
Importing an incorrectly formed certificate into the Keystore.
To overcome this problem, follow these steps:

In your command, use the right alias.
Check that the command refers to the Keystore by its exact name.
Check that the certificate is properly formatted. Open your certificate in a plain text editor (notepad, vim, etc.) as follows:
Between five dashes, the header and footer are included.
There are no spaces at the end of each line.
The certificate is saved in.p7b format.
When performing the import function, use the following syntax:
-alias name -file certificate file.p7b -Keystore Keystore name key tool -import -trustcacerts

Note: alias name is the alias for the private key in your Keystore, Keystore name is the path to your Keystore, and Keystore output.txt is the file that will be generated.
You’ll be required to enter the password for the key store.

Please follow the instructions below if you’ve forgotten your alias or need to double-check your Keystore information.
Run the following command to see the certificate details in a Keystore:
-keystore Keystore name key tool -list -v
Run the following command to save the certificate information in a Keystore to a text file:
> Keystore output.txt key tool -list -v -Keystore Keystore name

Where Keystore name is the name of your Keystore and Keystore output.txt is the name of the file that will be created.
You’ll be required to enter the password for the key store.

Note: If the error persists, make sure you’re using the correct Keystore file and alias. The final step will be to generate a new CSR and a new Keystore file from scratch. The SSL Certificate should be reissued, and then the SSL Certificate should be installed.