Configuring Managed WLS Servers to Use the Custom Keystores

9-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite

9.3.5 Configuring Managed WLS Servers to Use the Custom Keystores

Follow these steps to configure the identity and trust keystores for WLS_SERVER:

1. Log in to Oracle WebLogic Server Administration Console.

2. Click Lock Edit.

3. Expand the Environment node in the Domain Structure window.

4. Click Servers. The Summary of Servers page opens.

5. Click the name of the server for which you want to configure the identity and trust

keystores WLS_SERVER. The settings page for the selected server opens.

6. Select Configuration, then Keystores.

7. Click the Change button next to the Keystores field and select the Custom

Identity and Custom Trust method for storing and managing private keysdigital certificate pairs and trusted CA certificates. Click Save when you are done.

8. In the Identity section, define attributes for the identity keystore:

■ Custom Identity Keystore: The fully qualified path to the identity keystore: ORACLE_BASE admindomain_nameaserverdomain_namecerts appIdentityKeyStore.jks ■ Custom Identity Keystore Type: Leave blank; it defaults to JKS. ■ Custom Identity Keystore Passphrase: The password Keystore_Password you provided in Section 9.3.3, Creating a Trust Keystore Using the Keytool Utility. This attribute is optional or required depending on the type of keystore. All keystores require the passphrase in order to write to the keystore. However, some keystores do not require the passphrase to read from the keystore. WebLogic Server only reads from the keystore, so whether or not you define this property depends on the requirements of the keystore.

9. In the Trust section, define properties for the trust keystore:

■ Custom Trust Keystore: The fully qualified path to the trust keystore: ORACLE_BASE admindomain_nameaserverdomain_namecerts appTrustKeyStore.jks ■ Custom Trust Keystore Type: Leave blank; it defaults to JKS. ■ Custom Trust Keystore Passphrase: The password you provided as New_ Password in Section 9.3.3, Creating a Trust Keystore Using the Keytool Utility. This attribute is optional or required depending on the type of keystore. All keystores require the passphrase in order to write to the keystore. However, some keystores do not require the passphrase to read from the keystore. WebLogic Server only reads from the keystore, so whether or not you define this property depends on the requirements of the keystore.

10. Click Save.

11. Click Activate Changes in the Administration Consoles Change Center to make

the changes take effect.

12. Select Configuration, then SSL.

13. Click Lock Edit.

14. In the Private Key Alias field, enter the alias you used for the host name the

managed server listens on. Setting Up Node Manager 9-7 In the Private Key Passphrase and the Confirm Private Key Passphrase fields, enter the password for the keystore that you created in Section 9.3.2, Creating an Identity Keystore Using the utils.ImportPrivateKey Utility.

15. Click Save.

16. Click Activate Changes in the Administration Consoles Change Center to make

the changes take effect. 17. Restart the server for which the changes have been applied.

9.3.6 Changing the Host Name Verification Setting for the Managed Servers