Configuring a customPasswordEncryption provider for Liberty runtime environment

Enable the customPasswordEncryption provider to encrypt the sensitive strings.

Before you begin

Obtain an Enterprise Systems Architecture (ESA) file that contains the customPasswordEncryption provider. The ESA file implements the com.ibm.wsspi.security.crypto.CustomPasswordEncryption interface as described in Developing a customPasswordEncryption Provider. If you do not have an ESA file that contains the customPasswordEncryption provider, obtain a Java™ archive (JAR) file and one or more manifest files that include installation instructions. If you want to use the customPasswordEncryption provider with WebSphere® Developer Tools, make sure that the customPasswordEncryption provider enables the ESA file for developer tools.

About this task

Enable the customPasswordEncryption provider to encrypt the strings by using the customPasswordEncryption provider. The customPasswordEncryption provider encrypts strings in the server.xml file.

Procedure

Use installUtility command to install the ESA file.

If the customPasswordEncryption provider is packaged differently from the ESA file, follow the installation instructions for the customPasswordEncryption provider.
Enable the customPasswordEncryption provider feature in the server.xml file.
The owner of the customPasswordEncryption provider gives the name of the feature, as shown in the following example:
```
<featureManager>
     <feature>usr:customPasswordEncryption-1.0</feature>
</featureManager>
```

Start the server and verify that the CWWKS1850I message is logged in the messages.log file.

The following message is an example: [8/10/16 7:07:07:007 EDT] 0000001e com.ibm.ws.crypto.util.PasswordCipherUtil I CWWKS1850I:
The custom password encryption service has started. The class name is com.ibm.websphere.crypto.sample.customencryption.CustomEncryptionImpl.