Versions Compared

Old Version 28

changes.mady.by.user Former user

Saved on

compared with

New Version 29

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Maintain a primary keystore for encrypting sensitive data such as admin passwords and certain registry data. By default, the primary keystore is also used for WS-Security and for authenticating Tomcat level connections.
  • Maintain a separate keystore for authenticating the communication over SSL/TLS for Tomcat level connections.
  • Optionally, you can set up separate keystores with key pairs and certificates for WS-Security.
  • A separate keystore (truststore) for the purpose of storing the trusted certificates of public keys in your keystores.

See the related links for For information on creating new keystores with the required certificates, see the related links.

Default keystore settings in WSO2 products

...

Info

Note the following regarding WSO2 keystore management:

  • You cannot import an existing private key for which you already have a certificate.
  • You cannot delete the default wso2carbon.jks keystore.
  • You must have the same password for both keystore and private key due to a Tomcat limitation.
  • You cannot remove a service before disabling its security.

For information on how to create new keystore files, see Creating New Keystores, and for information on how to update configuration files in your product with keystore information, see Configuring Keystores in WSO2 Products.

Excerpt
hiddentrue

Note to Writers: The 'Related Links' title is bookmarked in the shared spaces so that it is also pulled along with the other content. Therefore, after pulling this page, make sure to add the relevant interspace links in your product spaces. Use the Children Display macro.