Open Liberty supports AES encryption for passwords that are stored in the
When you use this option for protecting passwords in the Open Liberty configuration, you need to understand the limits to the protection that AES encryption provides.
Encrypting a password in the Open Liberty configuration doesn’t guarantee that the password is secure or protected. When a password is encrypted, someone who can see the encrypted password can’t easily recover the password unless they know the encryption key. The application server process requires access to the encrypted password and the decryption key, so these items must be stored on the file system that is accessible to the server runtime environment. The encryption key is also required by anyone who encrypts a password that’s placed in the server configuration. If an attacker has access to the same set of files as the Open Liberty server, applying AES encryption to the password provides no additional security over XOR encoding. However, you might still consider encrypting passwords in the Open Liberty configuration.
The Open Liberty configuration is composable and sharable. It can be configured without an administration subsystem, so any XOR-encoded password is visible to any administrator. Because of these design features, consider whether passwords are sensitive and need to be encrypted. If passwords aren’t sensitive, encoding them might provide little value. If passwords are sensitive, protect the configuration files or the encoding key, depending on the scenario. Either the configuration files that contain the passwords are sensitive and access to these files must be controlled, or the passwords are encrypted and the encoding key is protected as sensitive.
For more information about how to obfuscate passwords for Open Liberty, see the securityUtility encode command.
In Open Liberty, the default key that’s used for encrypting and decrypting can be overridden by setting the
Make sure that you don’t set this property in the
server.xml file that stores the password.
Otherwise, the file that contains the key might be included when you run the
server dump or
server package commands.
Instead, set it in a separate configuration file that’s included by the
server.xml file, as shown in the following example:
<server> ... <include location="/protected/key.xml" /> </server>
This separate configuration file must contain only a single property declaration, and it must be stored outside the normal configuration directory for the server.