After you have created a new keystore and updated the
client-truststore.jks file, you must update a few configuration files in order to make the keystores work. Note that keystores are used for multiple functions in WSO2 products, which includes authenticating communication over SSL/TLS, encrypting passwords and other confidential information in configuration files etc. Therefore, you must update the specific configuration files with the updated keystore information. For example, you may have separate keystores for the purpose of encrypting passwords in configuration files, and for authenticating communication over SSL/TLS.
wso2carbon.jks keystore file, which is shipped with all WSO2 products, is used as the default keystore for all functions. However, in a production environment, it is recommended to create new keystores with new keys and certificates.
Please note that in WSO2 IoT Server and WSO2 Enterprise Integrator the
<PRODUCT_HOME>/repository/conf directory is in the following location:
If you want an easy way to locate all the configuration files that have references to keystores, you can use the
grep command as follows:
- Open a command prompt and navigate to the
<PRODUCT_HOME>/repository/conf/directory where your product stores all configuration files.
- Execute the following command:
grep -nr ".jks".
The configuration files and the keystore files referred to in each file are listed out. See an example of this below.
See the following for details:
Before you begin
- Be sure to go through the recommendations for setting up keystores in WSO2 products to understand the various keystores you will need.
- If you haven't already created the keystores required for your system, see the instructions for creating new keystores.
Configuring the primary keystore (for internal data encryption)
Encrypting administrator passwords as well as other confidential, internal information that are maintained in various product-level and product feature-level configurations/configuration files can be classified as internal data encryption. The
Keystore element in the
carbon.xml file, stored in the <
PRODUCT_HOME>/repository/conf/ directory should be updated with details of the keystore serving this purpose.
Be sure to use a keystore with a public key certificate that contains the Data Encipherment key usage as explained in the keystore recommendations. Otherwise, the following error can occur when you attempt data encryption:
The default configuration is shown below.
Configuring a separate keystore for internal data encryption
Currently, the keystore configured in the
<Security>/<KeyStore> element in the
<PRODUCT_HOME>/repository/conf/carbon.xml file is used for internal data encryption as well as for message signing and decryption when communicating external parties. You can separate these concerns and create a separate keystore to be used for internal data encryption.
Note: For some products, the
carbon.xml file may be located in
This feature is available via the WUM update 2792 released on the 8th of July 2018. This is available as part of the newly introduced Crypto Service. It is an extensible framework that facilitates the cryptography needs of WSO2 products. This is relevant for the following WSO2 products.
- WSO2 Identity Server 5.5.0
- WSO2 API Manager 2.2.0
- WSO2 Data Analytics Server 3.2.0
- WSO2 Enterprise Integrator 6.2.0
Warning: Using a totally new keystore for internal data encryption in an existing deployment will make already encrypted stored data unusable. In such cases, an appropriate data migration effort is needed.
A common use case of this feature for an existing deployment is to configure the existing keystore as the internal keystore for internal data encryption and using a new keystore when communicating with external parties such SAML, OIDC id_token signing.
Enable the Crypto Service by adding the following configuration block to the
Configure the new keystore by adding the following configuration block inside the
<Security>tag in the
Note: The values of the properties such as passwords must be changed based on the keystore.
Configuring a secondary keystore (for SSL connections)
catalina-server.xml file stored in the
<PRODUCT_HOME>/repository/conf/tomcat/ directory should be updated with the keystore used for certifying SSL connections to Carbon servers. Given below is the default configuration in the
catalina-server.xml file, which points to the default keystore in your product.
Configuring a keystore for Java permissions
The Java Security Manager is used for defining various security policies that prevent untrusted code from manipulating your system. Enabling the Java Security Manager for WSO2 products will activate the Java permissions that are in the
<PRODUCT_HOME>/repository/conf/sec.policy file. Administrators can modify this file to change the Java security permissions as required and grant various application-level permissions to the signed and trusted code using Java.
If you are granting specific Java-level permissions to some signed code, you should import the public key certificate of the signer as a trusted certificate to one of your keystores. You must then update the
sec.policy file with the keystore path and the alias of the certificate as shown below.
Following is the default keystore configuration in the sec.policy file, which grants all Java-level permissions to the code signed by the certificate that uses the “wso2carbon” alias.
Configuring keystores for WS-Security
If there are WS-Security scenarios implemented in your WSO2 product, you can use separate keystores for these scenarios. WS-Security is used for proxy services and data services in the ESB. See the documentation of WSO2 Enterprise Integrator (WSO2 EI) for instructions on applying security policies for proxy services, and data services.
Some WSO2 products will use keystore for more use cases than the ones listed above. See the documentation for your WSO2 product for instructions.