Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Secure communications > Create a keystore configuration for a preexisting keystore file
Manage keystore configurations remotely
We can manage keystores remotely in a WAS ND environment on separate machines. A node server can hold the configuration for a keystore, while the actual keystore resides on another system. After you set up a remotely managed configuration, you can perform all of the certificate and keystore operations for the keystore on the remote machine from the server that contains the keystore remote configuration. Key stores can be remotely managed only in network deployed environments.
Alternative Method: To manage a self-signed certificates by using wsadmin, use the PersonalCertificateCommands group commands of the AdminTask object. See the PersonalCertificateCommands command group article. Complete the following steps in the admin console:
Procedure
- Click Security > SSL certificate and key management > Manage endpoint security configurations > {Inbound | Outbound} > ssl_configuration > Key stores and certificates.
- Click New.
- Type a name in the Name field. This name uniquely identifies the keystore in the configuration.
- Type the location of the keystore file in the Path field. The location can be a file name or a file Uniform Resource Locator (URL) to an existing keystore file.
- Type the keystore password in the Password field. This password is for the keystore file specified in the Path field.
- Type the keystore password again in the Confirm Password field to confirm the password.
- Select a keystore type from the list. The type you select is for the keystore file specified in the Path field.
- Select the Remotely managed check box, and then fill in one or more hosts names of the systems where the keystore file is to be located. If provided multiple host names, separate the host names with a pipe (|).
- Select any of the following optional selections:
- The Read only selection creates a keystore configuration object but does not create a keystore file. If this option is selected, the keystore file specified in the Path field must already exist.
- The Initialize at startup selection initializes the keystore during run time.
- Select Apply and Save.
Results
A keystore configuration object is created on the server from where the command was run. The keystore file for the configuration will be created on each system specified in the host list.
What to do next
Now, you can perform all certificate management operations on the keystore from the system where the keystore configuration resides. For example, you can perform certificate management operations, such as: creating a self-signed certificate, extracting a certificate, or extracting a signer certificate.
Extract a signer certificate from a personal certificate
Create a self-signed certificate
Related
PersonalCertificateCommands command group