Configure a Red Hat Directory Server as a Key Store
Contents
casso127
Contents
2
You can configure Red Hat Directory Server as a separate key store.
Key Store Prerequisites
- Create a directory server instance that is to function as the key store. Be sure to create a root suffix and root object to store the keys.
- Create an LDAP user with privileges to create the schema, and read, modify, and delete objects in the LDAP tree underneath the key store root object.
Register the Key Store
casso127
Registering the key store configures a connection between the key store and the Policy Server. The Policy Server uses the credentials that you supply to manage the key store.
Important!
Registration does not configure the Policy Server to use the separate key store. The settings do not take effect until the Policy Server is restarted. Do not restart the Policy Server until the key store is configured and you are ready to deploy it.Follow these steps:
- Log in to the Policy Server host system.
- Run the following command to configure the connection:smldapsetup reg -hhost -pport -dadmin_user -wadmin_password -rroot -k1casso127If User Account Control (UAC) is enabled in Windows Server, open the command-line window with administrator permissions. Open the command-line window this way even if your account has administrator privileges.Example:smldapsetup reg -host172.16.0.0 -p389 -d"cn=directory manager" -wpassword -r"dc=test" -k1
- Start the Policy Server Management Console and open the Data tab.
- Complete one of the following procedures:
- If the Policy Server is configured to use a data relational database:
- Select Keystore from the Database list.
- Select LDAP from the Storage list to display the connection settings and administrative credentials.
- Verify that the connection settings and administrative user setting appear.
- Click test LDAP Connection to verify that the Policy Server can communicate with the key store instance.
- If the Policy Server is configured to use a directory server:a. Select Keystore from the Database list.b. Verify that the connection settings and the administrative user settings appear.c. Click test LDAP Connection to verify that the Policy Server can communicate with the key store instance.
The Use Policy Store database setting is cleared. The cleared setting is expected normal behavior. The Policy Server continues to use the key store that is collocated with the policy store. - Exit the Policy Server Management Console.The separate key is registered with the Policy Server.
Create the Key Store Schema
casso127
The key store instance requires the schema to store and retrieve
CA Single Sign-On
web agent keys. Use the smldapsetup utility to create the key store schema file.Follow these steps:
- Log in to the Policy Server host system.
- Run the following command to create the key store schema file:smldapsetup ldgen -ffile_name -k1casso127If User Account Control (UAC) is enabled in Windows Server, open the command-line window with administrator permissions. Open the command-line window this way even if your account has administrator privileges.Example:smldapsetup ldgen -fkeystoreschema -k1The key store schema file is created.
Import the Key Store Schema
The key store instance requires the schema to store and retrieve
CA Single Sign-On
web agent keys. Use the smldapsetup utility to import the key store schema file.Follow these steps:
- Log in to the Policy Server host system.
- Run the following command to import the key store schema:smldapsetup ldmod -ffile_name -k1Note:Standard out displays all policy store schema being imported. The behavior is normal and expected. The utility only imports the key–store specific schema. The utility only imports the key–store specific schema.Example:smldapsetup ldmod -fkeystoreschema -k1The key store–specific schema is imported.
- Complete the following steps:
- Restart the directory server. Restarting the directory server is required to save the key store schema correctly.
- Repeat step 2. Restarting the directory server removed the key store root. Importing the key store schema again is required to create the key store root.
Restart the Policy Server
casso127
The Policy Server continues to use the collocated key store until you restart the Policy Server. Restart the Policy Server to begin using the separate key store.