All WSO2 products, by default, come with a secure vault implementation, which is a modified version of synapse secure vault. It provides capability to securely store-sensitive data such as plain-text passwords in configuration files of the WSO2 Carbon platform, such as
registry.xml etc. All WSO2 Carbon-based products inherit the secure vault implementation from the core Carbon platform. For more information, see Securing Passwords in Configuration Files.
However, when securing passwords of more product-specific configuration files such as data service configurations, the steps may vary. Therefore, WSO2 DSS provides the feature to securely store sensitive data in data service configuration files, using the secure vault functionality. Users can encrypt their passwords using tokens instead of the actual password inside the data service configuration file. See the instructions given below.
If you create the datasource via the Configure → Datasources → Add Datasource option in the Management Console, it stores the datasource in the Registry, and thereby, the password you enter will be encrypted automatically.
- Run ciphertool script from
- Linux: sh ciphertool.sh -Dconfigure
- Windows: ciphertool.bat -Dconfigure
- To encrypt the plain text using ciphertool, run the ciphertool script again without
-Dconfigureoption. It asks for the KeyStore Password of the running Carbon instance. The default is
- Then provide the plain text value that needs to be encrypted and the tool returns the encrypted text value.
- Update the
<PRODUCT_HOME>/repository/conf/security/cipher-text.propertiesfile by adding a new alias (any name of your preference) and the encrypted value.
- Log in to the Management Console and click Main.
- Click List under the Services menu and click on the service whose password you want to secure.
- Click Edit Data Service (Wizard), click Next, and then click Edit Datasource.
- In the Edit datasource window of the management console select Use as Secret Alias option. In the Password field, provide the alias name instead of the actual password.
- The namespace and alias will be added to the .dbs file as follows: