If the directory/file paths specified in this guide do not exist in your WSO2 product, see Directory Structure of WSO2 Products to locate the paths applicable to your product.
Page Comparison - Using Asymmetric Encryption (v.59 vs v.60) - Administration Guide 4.4.x - WSO2 Documentation
Administration Guide 4.4.x

Versions Compared

Old Version 59

changes.mady.by.user Nilmini Perera

Saved on

compared with

New Version 60

changes.mady.by.user Nilmini Perera

Saved on

Key

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

...

Note

For information on creating new keystores with the required certificates, 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.

Managing keystores 

WSO2 products provide the facility to add keystores using the management console or using an XML configuration, and to import certificates to the keystore using the management console. The WSO2 keystore management feature provides a UI and an API to add and manage keystores. For example, when you apply WS-Security to Web services using the management console, you can select a keystore for encryption/signing processes from the uploaded keystores. The management console also allows you to view/delete keystores. 

All the functions of keystore management are exposed via APIs. As a result, if you are writing a custom extension to a WSO2 product (e.g., for WSO2 ESB mediators), you can directly access the configured keystores using the API. The API hides the underlying complexity, allowing you to easily use it in third-party applications to manage their keystores as well.