Using Vault instead of cleartext password in WildFly configuration file in RSA Identity Governance & Lifecycle
WildFly based RSA Identity Governance & Lifecycle deployments, e.g., Software Bundle, by default use cleartext passwords for keystores in a configuration file. The cleartext passwords for keystores should be secured in the configuration file.
In WildFly based deployments of RSA Identity Governance & Lifecycle, the cleartext password values for keystores can be secured by masking and persisting in a Vault store and then using references to the Vault store instead of the cleartext passwords in the configuration file.
The procedure to configure a Vault store and replace cleartext passwords with references to the Vault store in WildFly configuration file is available on request. Please contact RSA Customer Support and quote this knowledgebase article number to request the procedure (WildFly-Vault-KB000065818-20220330.pdf).
Make a note of the following, if the procedure to replace cleartext passwords with references to a vault store has been followed for an RSA Identity Governance & Lifecycle deployment:
On applying a patch, the vault configuration in WildFly will not be impacted.
On upgrading to a later version, the procedure must be followed again after the upgrade to replace cleartext passwords with the vault references.
For backup/restore, ensure to backup the vault store and the updated WildFly configuration file, and then restore those files after a recovery/reinstallation of RSA Identity Governance & Lifecycle.
Read and use the information in this RSA Security Advisory to assist in avoiding any situation that might arise from the problems described herein. If you have any questions regarding this product alert, contact RSA Software Technical Support at 1- 800 995 5095. RSA Security LLC and its affiliates, including without limitation, its ultimate parent company, Dell EMC, distributes RSA Security Advisories in order to bring to the attention of users of the affected RSA products, important security information. RSA recommends that all users determine the applicability of this information to their individual situations and take appropriate action. The information set forth herein is provided 'as is' without warranty of any kind. RSA disclaims all warranties, either express or implied, including the warranties of merchantability, fitness for a particular purpose, title and non-infringement. In no event, shall RSA, its affiliates or suppliers, be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if RSA, its affiliates or suppliers have been advised of the possibility of such damages. Some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, so the foregoing limitation may not apply.