Complete the following steps to create your CSR. Before you can create your CSR, you need to create your Java keystore. Your Java keystore contains your private key. Run the following command to create your 2048 bit Java keystore: keytool -genkey -alias myalias -keyalg RSA –keysize 2048 -keystore c: yoursite.keystore 2. Open a command prompt in the same directory as Java keytool; alternatively, you may specify the full path of keytool in your command. Pay close attention to the alias you specify in this command as it will be needed later on. Keytool -genkey -alias mydomain -keyalg RSA -keystore KeyStore.jks -keysize 2048 2. Generate a CSR based on the new.
SSL Certificate CSR Creation for Java Based Web Servers.Keytool Certreq Example
If you already have your SSL Certificate and just need to install it, see
SSL Certificate Installation :: Java Web Servers.
How to generate a CSR using Java Keytool
**NOTE: You must generate a new keystore through this process. If you try to install a new certificate to an old keystore your certificate will not work properly. Backup and remove any old keystores if necessary before beginning this process.
Recommended: Save yourself some time by using our new Java Keytool CSR Wizard to create your CSR with Keytool. Just fill in the details, click Generate, and paste your customized keytool command into your terminal.
If you prefer to roll your own keytool commands to generate your CSR, just follow our old instructions below:
Create a New Keystore
Generate Your CSR with Your New keystore
Generating a CSR for Issuance of an SSL Certificate with Keytool
How to generate a Certificate Signing Request for your Java Web Server
Keytool Utility:Create Keystore Keytool
Keytool is a key and certificate management JDK utility which helps in managing a keystore of private/public keys and associated certificates. It allows users to administer their own public/private key pairs and associated certificates for use in self-authentication (where the user authenticates himself/herself to other users/services) or data integrity and authentication services, using digital signatures. It also allows users to cache the public keys (in the form of certificates) of their communicating peers.
Java Keytool stores the keys and certificates in what is called a keystore. Java keystore is implemented as a file by default. It protects private keys with a password.
keytool also enables users to administer secret keys used in symmetric encryption/decryption (e.g. RSA,DES).
A Keytool keystore contains the private key and any certificatesnecessary to complete a chain of trust and establish the trustworthiness of the primary certificate.
All certificates in a Java keystore is associated with a unique alias. Which will be used as a pointer to later perform any of the keytool operation to import/export/delete/change certificates/key etc.
Keytool Options:
The various keytool options are listed below
Various Steps to process the Keystore , CSR and the signed certificate.
Create a keystore using Keytool:
While we create a Java keystore we will first create the .jks file that will initially only contain the private key using keytool utility.
-alias is an option to mention an Alias Name to your key entry
-keyalgspecifies the algorithm to be used to generate the key pair
-keysizespecifies the size of each key to be generated.
-sigalg specifies the algorithm that should be used to sign the self-signed certificate; this algorithm must be compatible with keyalg.
![]()
–validityspecifies the validity of the keystore which you want to create.
When you execute the command we will be prompted with question which we need answer to add as the key details such as Common Name(website/Application dns name), Organisation, Country,State, province, Country code etc. This is user defined values. Also it will be prompt you to enter keystore and key password which should be used in future to read/write/modify the keystore.
As the keystore name is mentioned keystore.jks while creating keystore.jks file will be created in the current folder.
Use below command to list the entries in keystore to view the content. We will be able to see the entered values reflected on the private key entries on the keystore.jks file.
Generate a CSR (Certificate Signing Request) from keystore:
Next step is to create a Certificate Signing Request(CSR) from the created keystore to share with Certificate Authority(CA) to sign and generate the Primary/Server certificate.
We need to pass the correct alias name and password which we mentioned during the creation of the keystore to extract the certificate request.
Generate Signed Primary/Server Certificate from Certificate Authority
Submit the generated CSR to any of the CA authority which is supported by the SSL community to get the signed the Primary/Server certificate. The CA authority will be selected based on the organisations or your personnel selection.
Top 10 Certificate Authority in the world (Info based on 2017 from wikipedia)
Import the Primary/Server certificate, root and intermediate CA certificates to keystore
Once the CA signed the certificate and share it with us, we need to import the certificate to the keystore for the privatekey entry we created.
Below keytool commands can be used to import the signed certificate to keystore, we should use the alias name same as the alias name on the private key entry.
Second one is optional using -trustcacerts.
If the –trustcacerts option has been specified, additional certificates are considered for the chain of trust, namely the certificates in a file named “cacerts”
If the alias does not point to a key entry, then keytool assumes you are adding a trusted certificate entry. In this case, the alias should not already exist in the keystore. If the alias does already exist, then keytool outputs an error, since there is already a trusted certificate for that alias, and does not import the certificate.
If the alias points to a key entry, then keytool assumes you are importing a certificate reply.
![]()
The old chain can only be replaced if a valid keypass, the password used to protect the private key of the entry, is supplied. If no password is provided, and the private key password is different from the keystore password, the user will be prompted for it.
Import a root or intermediate CA certificate to an existing Java keystore
entrust(CA) is used as an example, File will be different and supplied by the Certificate Authority(CA) based on your CA.
To View/List the certificate we have added below command can be usedKeytool Generate Key And CsrShare the certificate or root certificates to system which use the SSL to communicate to your system/application.Keytool Generate Csr From Keystore
As you have created a new Private/Public key for you DNS name we need to share the certificate with any of the interfacing applications (Not Browser as it will be having CA root/intermediate on its list).
Important commands for keytool which can be used while create/import/export/delete/change certificate in a keystore.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |