WSO2 products use asymmetric encryption by default for the purposes of authentication and data encryption. In asymmetric encryption, keystores (with key pairs and certificates) are created and stored for the product. It is possible to have multiple keystores so that the keys used for different use cases are kept unique. For more information about creating and configuring keystores, see Using Asymmetric Encryption.
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 keystore work.
For instructions on the default carbon keystore configurations, see Configuring Keystores in WSO2 Products in the WSO2 Product Administration Guide.
Follow the steps below to configure a keystore in WSO2 API Manager.
Configuring keystores for AMQP and MQTT transports
To configure AMQP and MQTT transports, open
<API-M_HOME>/repository/conf/broker.xml. The values for the
password parameters under
trustStore should be updated. The code below shows the default values.
Configuring keystores for Jaggery Apps SSO configuration
<API-M_HOME>/repository/deployment/server/jaggeryapps/publisher/site/conf/site.json. Update the values for
keyStorePassword as shown below.
Configuring keystores for endpoints
EndpointConfig.properties and update
client.trustStore with the location of the keystore and truststore, respectively. The default configurations are shown below.
Configuring keystores for advanced transport handling
To have more advanced transport handling functions using keystores, you need to update the
<API-M_HOME>/repository/conf/tomcat/catalina-server.xml file and the