WSO2 Carbon is shipped with a Secure Vault implementation, which is a modified version of synapse Secure Vault. This allows you to store encrypted passwords that are mapped to aliases. That is, you can use the aliases instead of the actual passwords in your configuration files for better security. For example, some configurations require the admin username and password. If the admin user password is "admin", you could use the alias
UserManager.AdminUser.Password in your configuration file. You would then map that alias to the actual password "admin". At runtime, the product will look up this alias in the secure vault and then decrypt and use its password.
Some of the important elements in the secure vault implementation, which are used in Carbon products for encrypting plain text passwords are as follows:
- This is used to store the secret values (encrypted values). T he
cipher-text.propertiesfile, located in the
<PRODUCT_HOME>/repository/conf/securityfolder is the default file based secret repository used by the Secret Manager in your Carbon product. Note that, currently, Secure Vault only implements file based secret repositories. The Secret Repository stores aliases vs. their actual secrets in encrypted format (encrypted via a key in keystore). Any secret repositories can be written by implementing the SecretRepository and SecretRepositoryProvider classes. See the topic on creating custom secure vault configurations. Secret Repository:
cipher-text.propertiesfile. The keystore is required to create the decryption crypto, which can be used to resolve encrypted secret values. The keystore and Secret Repository are configurable through the
secret-conf.propertiesfile, which is created in the
<PRODUCT_HOME>/repository/conf/securityfolder when you execute the Cipher Tool.
Secret Manger: The Secret Manager initializes the Secret Repository and the keystore configured for the Carbon server. The secrets stored in the Secret Repository are accessed using the aliases indicated in the
- This provides the actual password for a given alias. There is a
SecretManagerSecretCallbackHandler, which is combined with Secret Manager to resolve the secret. Any callback can be written by implementing the
SecretCallbackHandlerclass. See the topic on creating custom secure vault configurations. Secret Callback:
- Secret Resolver: Any configuration builder that uses secret information within its own configuration file needs to initialize the Secret Resolver when building its own configuration. The Secret Resolver keeps a list of secured elements that need to be defined in the configuration file with secret aliases. Secret Resolver initializes the Secret Callback handler class, which is defined in the configuration file.
Create custom Secure Vault configuration
You can implement your own Secure Vault configurations by implementing a new secret repository, secret callback handler or by changing the keystore that is used for encryption. By default, the primary keystore of the product is used for encrypting and decrypting. You can find out more about working with keystores from here.
Writing a new secret callback handler
Let's see how we can write a new Secret Callback Handler class to secure the user management and registry database connection password. In this sample, you do not need to configure a Secret Repository or keystore (cipher-text.properties) as you are not going to store the secret or encrypted values.
Write a Secret Callback class. You need to implement the
SecretCallbackHandlerinterface or extend the
AbstractSecretCallbackHandlerabstract class. For example,
We can set multiple passwords:
- Create a JAR or an OSGI bundle and copy the JAR file to the
<PRODUCT_HOME>/repository/component/lib/directory or the OSGI bundle to the
master-datasources.xmlfile with an alias name and your Secret Callback handler class name. For example,
Also, replace the secret callback handler class name in
<PRODUCT_HOME>/repository/conf/security/secret-conf.propertiesfile with your Secret Callback handler class name.
- Restart the server.