Creating a Keystore Using Fusion Middleware Control

Managing Keystores, Wallets, and Certificates 8-9

8.3.3.6 Deleting a Keystore Using WLST

Assuming the application server instance name is inst1, use this command to delete a keystore: deleteKeyStoreinst1, ovd5, ovd, demo where the component type is ovd, the component instance is ovd5, and the keystore is named demo.

8.3.3.7 Importing a Keystore Using Fusion Middleware Control

1. Navigate to the Java Keystores page for the component instance, as explained in Section 8.3.3.1, Creating a Keystore Using Fusion Middleware Control. 2. Click Import. 3. The Import Keystore dialog box appears. 4. Browse the file system to locate the keystore file. 5. Provide a name for the keystore. Enter the keystore password. 6. Click OK. 7. The imported keystore appears in the list of Java keystores.

8.3.3.8 Importing a Keystore Using WLST

Assuming the instance name is inst1, use this command to import a keystore: importKeyStoreinst1, ovd5, ovd, demojks, password, tmpdemojks.jks where password is the password for this keystore.

8.3.3.9 Changing the Keystore Password Using Fusion Middleware Control

Take these steps to change a keystore password: 1. Navigate to the Java Keystores page for the component instance, as explained in Section 8.3.3.1, Creating a Keystore Using Fusion Middleware Control. 2. Select a keystore and click Change Password. See Also: Section 6.9.8, deleteKeyStore . See Also: Section 6.9.18, importKeyStore . 8-10 Oracle Fusion Middleware Administrators Guide 3. A dialog box appears on which you must enter the current password and enter a new password. The new password must be entered a second time to confirm. 4. Click OK to change the password. In future, any operations performed on this keystore or its certificates will require the use of the new password.

8.3.3.10 Changing the Keystore Password Using WLST

Assuming the instance name is inst1, use this command to change the keystore password: changeKeyStorePasswordinst1, ovd5, ovd, demojks, current_password, new_password where current_password is the current password for this keystore, and new_ password is the new password.

8.3.4 Managing the Certificate Life Cycle

Typical life cycle events for a certificate residing in a keystore are as follows: ■ A self-signed certificate is automatically created for the keypair. ■ A certificate signing request CSR is generated, and can then be exported to a file. ■ Certificates are imported into the keystore. A certificate can either be pasted into a text box or imported from the file system. You can import both user certificates and trusted certificates also known as CA certificates in this way. ■ Certificates or trusted certificates are exported from the keystore out to a file. ■ Certificates or trusted certificates are deleted from the keystore.

8.3.5 Common Certificate Operations

This section describes the following common certificate operations: ■ Generating a New Key for the Keystore Using Fusion Middleware Control ■ Generating a New Key for the Keystore Using WLST ■ Generating a Certificate Signing Request Using Fusion Middleware Control ■ Generating a Certificate Signing Request Using WLST ■ Importing a Certificate or Trusted Certificate into a Keystore Using Fusion Middleware Control ■ Importing a Certificate or Trusted Certificate into a Keystore Using WLST See Also: Section 6.9.3, changeKeyStorePassword .