WSO2 Carbon-based products are shipped with a default keystore named wso2carbon.jks , which is stored in the
<PRODUCT_HOME>/repository/resources/security directory. This keystore comes with a private/public key pair that is used for all purposes, such as encrypting sensitive information, for communication over SSL and for message encryption/signing purposes in WS-Security. You can either use one new keystore for all purposes in your product, or you can create multiple keystores for each purpose.
Let's start creating a new keystore:
Before you begin
Go through the recommendations for setting up keystores in WSO2 products to understand the type of keystores you need.
If you are creating a new keystore for data encryption, be sure to acquire a public key certificate that contains the Data Encipherment key usage as explained in the keystore recommendations.
Creating a keystore using an existing certificate
Secure Sockets Layer (SSL) is a protocol that is used to secure communication between systems. This protocol uses a public key, a private key and a random symmetric key to encrypt data. As SSL is widely used in many systems, certificates may already exist that can be reused. In such situations, you can use an already existing CA-signed certificate to generate your keystore for SSL by using OpenSSL and Java keytool.
First, you must export certificates to the PKCS12/PFX format. Give strong passwords whenever required.
In WSO2 products, it is a must to have the same password for both thekeystoreand private key.
Execute the following command to export the entries of a trust chain into a keystore of .pfx format:
Convert the PKCS12/PFX formatted keystore to a Java keystore using the following command:
Now you have a keystore with a CA-signed certificate.
Creating a keystore using a new certificate
If there are no certificates signed by a Certification Authority, you can follow the steps in this section to create a keystore for SSL using a new certificate. We will be using the keytool that is available with your JDK installation.
Step 1: Creating keystore with private key and public certificate
- Open a command prompt and go to the
<PRODUCT_HOME>/repository/resources/security/directory. All keystores should be stored here.
Create the keystore that includes the private key by executing the following command:
This command will create a keystore with the following details:
- Keystore name: newkeystore.jks
- Alias of public certificate: newcert
- Keystore password: mypassword
- Private key password: mypassword (this is required to be the same as keystore password)
Note that if you did not specify values for the '-keypass' and the '-storepass' in the above command, you will be asked to give a value for the '-storepass' (password of the keystore). As a best practice, use a password generator to generate a strong password. You will then be asked to enter a value for -keypass. Click Enter because we need the same password for both the keystore and the key. Also, if you did not specify values for -dname, you will be asked to provide those details individually.
- Open the
<PRODUCT_HOME>/repository/resources/security/directory and check if the new keystore file is created. Make a backup of it and move it to a secure location. This is important as it is the only place with your private key.
Step 2: Creating CA-signed certificates for public key
Now we have a .jks file. This keystore (.jks file) can be used to generate a certificate signing request (CSR). This CSR file must be certified by a certificate authority or certification authority (CA), which is an entity that issues digital certificates. These certificates can certify the ownership of a public key.
Execute the following command to generate the CSR:
As mentioned before, use the same alias that you used during the keystore creation process.
You will be asked to give the keystore password. Once the password is given, the command will output the newcertreq.csr file to the
<PRODUCT_HOME>/repository/resources/security/directory. This is the CSR that you must submit to a CA.
You must provide this CSR file to the CA. For testing purposes, try the 90 days trial SSL certificate from Comodo.
It is preferable to have a wildcard certificate or multiple domain certificates if you wish to have multiple subdomains like gateway.sampledomain.org, publisher.sampledomain.org, identity.sampledomain.org, etc., for the deployment. For such requirements, you must modify the CSR request by adding subject alternative names. Most of the SSL providers give instructions to generate the CSR in such cases.
After accepting the request, a signed certificate is provided along with a root certificate and several intermediate certificates (depending on the CA) as a bundle (.zip file).
Step 3: Importing CA-signed certificates to keystore
Before importing the CA-signed certificate to the keystore, you must add the root CA certificate and the two (related) intermediate certificates by executing the commands given below. Note that the sample certificates given above are used as examples.
Optionally we can append the
-storepass <keystore password>option to avoid having to enter the password when prompted later in the interactive mode.
After you add the root certificate and all other intermediate certificates, add the CA-signed SSL certificate to the keystore by executing the following command:
In this command, use the same alias (i.e., 'newcert') that you used while creating the keystore
Now you have a Java keystore, which includes a CA-signed public key certificate that can be used for SSL in a production environment. Next, you may need to add the same CA-signed public key certificate to the
client-truststore.jks file. This will provide security and trust for backend communication/inter-system communication of WSO2 products via SSL.
Adding a public key to client-truststore.jks
<PRODUCT_HOME>/repository/resources/security/). In case we need to import a public key certificate into the trust store, you can achieve this using keytool as explained below. In this example, we are importing the same CA-signed public key certificate (which we obtained above) into
Note that we are using the default client-truststore.jks file in your WSO2 product as the trust store in this example.
- Get a copy of the
client-truststore.jksfile from the
Export the public key from your .jks file using the following command.
Import the public key you extracted in the previous step to the
client-truststore.jksfile using the following command.
Note that 'wso2carbon' is the keystore password of the default client-truststore.jks file.
Now, you have an SSL certificate stored in a Java keystore and a public key added to the
client-truststore.jks file. Note that both these files should be in the
<PRODUCT_HOME>/repository/resources/security/ directory. You can now replace the default wso2carbon.jks keystore in your product with the newly created keystore by updating the relevant configuration files in your product. For information on the concepts of keystores and about how keystores are used in WSO2 products, see Using Asymmetric Encryption.
Once you have created a new keystore in your product as explained above, update the relevant configuration files as explained in Configuring Keystores in WSO2 Products.