Keystores allow you to manage the keys that are stored in a database. A Keystore must contain a key pair with a certificate signed by a trusted Certification Authority (CA). A CA is an entity trusted by all parties participating in a secure communication. This entity will certify the trusted party's public keys by signing them. Since the certificate authority is trusted, it will accept the public key certificates signed by that particular CA as trusted. WSO2 Carbon uses several keystores to power the HTTPS transport and to encrypt other confidential information such as administrator passwords.
Keystore of the HTTPS transport
The keystore of the HTTPS transport is configured in the
axis2.xml file under the HTTPS transport receiver and HTTPS transport sender configurations.
The default keystore named
wso2carbon.jks, can be found in the <
PRODUCT_HOME>/repository/resources/security directory. To change the keystores used by the HTTPS transport, update the HTTPS transport receiver and sender configurations by specifying the paths to keystores files and other attributes of the files such as the keystores passwords.
Under the <
KeyStore> element two password values must be specified.
Password> element should indicate the password of the keystore file.
KeyPassword> element should point to the password required to access the private key.
Keystore for encrypting confidential information
The keystores used to encrypt administrator passwords and other confidential information in Carbon is configured in the <
PRODUCT_HOME>/repository/conf/carbon.xml file. These keystore configurations can be found under the <
security> element of the
Keystore for SSL connection to server
The keystore configuration used to store the certified keys for the SSL server connection is as follows.
Keystore for encrypting to registry
The keystore configuration used for encrypting meta data into the registry in Carbon is as follows.