Installation and Upgrade Guides › Policy Server Installation Guide › Configuring LDAP Directory Servers to Store CA SiteMinder® Data › How to Configure Oracle Virtual Directory as a Policy Store

How to Configure Oracle Virtual Directory as a Policy Store

Oracle Virtual Directory (OVD) can function as a policy store. A single directory server instance can function as a:

• Policy store
• Key store

Using a single directory server simplifies administration tasks. This scenario describes how to configure a single directory server instance to store policy data and encryption keys.

Note: If your implementation requires, you can configure a separate key store.

To configure Oracle Virtual Directory as a policy store, do the following procedures:

1. Gather directory server information
2. Extend the Oracle Virtual Directory local schema with CA SiteMinder® schema files.
3. Create an Oracle Virtual Directory adapter to connect to the existing policy store.
4. Point the Policy Server to the directory server.
5. Set the CA SiteMinder® superuser password.
6. Restart the Policy Server.
7. Prepare for the Administrative UI registration.

Gather Directory Server Information

Configuring an LDAP directory server as a policy store or upgrading an existing policy store requires specific directory server information. Gather the following information before beginning. You can use the Policy Store Worksheets to record your values.

Note: Policy and data store worksheets are provided to help you gather and record information before configuring or upgrading a CA SiteMinder® data store. You can print the applicable worksheet and can use it to record required information before beginning.

Host information

Specifies the fully-qualified host name or the IP Address of the directory server.

Port information

(Optional) Specifies a non-standard port.

Default values: 636 (SSL) and 389 (non-SSL)

Administrative DN

Specifies the LDAP user name of a user who has privileges to create, read, modify, and delete objects in the LDAP tree underneath the policy store root object.

Administrative password

Specifies the password for the Administrative DN.

Policy store root DN

Specifies the distinguished name of the node in the LDAP tree where policy store objects are to be defined.

SSL client certificate

Specifies the pathname of the directory where the SSL client certificate database file resides.

Limit: SSL only

Extend the OVD Local Schema With the CA SiteMinder® Schema Files

Extend the Oracle Virtual Directory with the following CA SiteMinder® schema files:

• ovd_sm_schema.ldif
• ovd_xps_schema.ldif

Follow these steps:

1. Log in to the Policy Server host system.
2. Navigate to siteminder_home/db/tier2/Oracle Virtual Directory and copy the following file to the OVD host system:

   ovd_sm_schema.ldif
   

3. Navigate to siteminder_home/xps/db/schema_extension/db/Oracle Virtual Directory and copy the following file to the OVD host system.

   ovd_xps_schema.ldif
   

4. Log in to the Oracle Virtual Directory system.
5. Have the administrator of your directory server run the following commands to extend the local schema with the CA SiteMinder® schema files:

   ldapmodify -h OVD_Host -p OVD_Port -D cn=Admin -w Admin_Password -v -a -f ovd_sm_schema.ldif
   

   ldapmodify -h OVD_Host -p OVD_Port -D cn=Admin -w Admin_Password -v -a -f ovd_xps_schema.ldif
   

   dsconf reindex -h localhost -p OVD_Port -e "ou=Netegrity,root_database"
   

   OVD_Host

   Specifies the OVD system IP Address or fully qualified domain name.

   OVD_Port

   Specifies the port on which the OVD instance is running.

   cn=Admin

   Specifies the OVD server admin with rights to modify the schema.

   Admin_Password

   Specifies the server admin password.

Create an Oracle Virtual Directory Adapter to Connect to Existing Policy Store

To create an Oracle Virtual Directory LDAP adapter to connect to your existing policy store, use the Oracle Directory Services Manager.

Follow these steps:

1. Log in to Oracle Directory Services Manager.
2. Select Adapter from the task selection bar. The Adapter navigation tree appears.
3. Click the Create Adapter button. The New Adapter Wizard appears.
4. Specify the following values on the Type screen:

   Adapter Type

   Select LDAP.

   Adapter Name

   Enter a unique name for the LDAP adapter.

   Adapter Template

   Select an adapter template that corresponds to the directory type of the existing policy store.

5. Click Next.
6. Enter the following values on the Connection screen (accept the defaults for all other settings):

   Use DNS for Auto Discovery

   Select No.

   Host

   Enter the hostname or IP address of the remote host.

   Port

   Enter the port at which the remote host instance is running.

   Server proxy Bind DN

   Enter the credentials of a directory user who has permission to modify directory contents.

   Proxy Password

   Password for the user that is specified in the Secure proxy Bind DN field.

7. Click Next.
8. On the Connection Test screen, click Next if the connection status is OK. Otherwise, click Back and troubleshoot your connection settings.
9. Enter the following values on the Namespace screen (accept the defaults for all other settings):

   Remote Base:

   Click Browse and select the DN at which the policy data is stored.

   Mapped Namespace

   Enter a local DN at which to map the policy data.

10. Review the Summary page and click Finish.

Point the Policy Server to the Policy Store

You point the Policy Server to the policy store so the Policy Server can access the policy store.

Follow these steps:

1. Open the Policy Server Management Console.

   Important! If you are accessing this graphical user interface on Windows Server 2008, open the shortcut with Administrator permissions. Use Administrator permissions even if you are logged in to the system as an Administrator. For more information, see the release notes for your CA SiteMinder® component.

2. Click the Data tab.
3. Select the following value from the Database list:

   Policy Store
   

4. Select the following value from the Storage list:

   LDAP
   

5. Configure the following settings in the LDAP Policy Store group box.
   • LDAP IP Address
   • Admin Username
   • Password
   • Confirm Password
   • DN

   Note: You can click Help for a description of fields, controls, and their respective requirements.

6. Click Apply.
7. Click Test LDAP Connection to verify that the Policy Server can access the policy store.
8. Click OK.

Set the CA SiteMinder® Super User Password

The default CA SiteMinder® administrator account is named:

siteminder

The account has maximum permissions.

We recommend that you do not use the default superuser for day–to–day operations. Use the default superuser to:

• Access the Administrative UI for the first–time.
• Manage CA SiteMinder® utilities for the first–time.
• Create another administrator with superuser permissions.

Follow these steps:

1. Copy the smreg utility to siteminder_home\bin.

   siteminder_home

   Specifies the Policy Server installation path.

   Note: The utility is at the top level of the Policy Server installation kit.

2. Run the following command:

   smreg -su password
   

   password

   Specifies the password for the default CA SiteMinder® administrator.

   Limits:

   • The password must contain at least six (6) characters and cannot exceed 24 characters.
   • The password cannot include an ampersand (&) or an asterisk (*).
   • If the password contains a space, enclose the passphrase with quotation marks.

   Note: If you are configuring an Oracle policy store, the password is case–sensitive. The password is not case–sensitive for all other policy stores.

3. Delete smreg from siteminder_home\bin. Deleting smreg prevents someone from changing the password without knowing the previous one.

   The password for the default CA SiteMinder® administrator account is set.

More information:

Locate the Installation Media

Installation Media Names

Enable the Advanced Authentication Server

Enable the advanced authentication server as part of configuring your Policy Server.

Follow these steps:

1. Start the Policy Server configuration wizard.
2. Leave all the check boxes in the first screen of the wizard cleared.
3. Click Next.

   The master key screen appears.

4. Create the master encryption key for the advanced authentication server.

   Note: If you are installing another (nth) Policy Server, use the same encryption key for the Advanced Authentication server that you used previously.

5. Complete the rest of the Policy Server configuration wizard.

   The advanced authentication server is enabled.

Restart the Policy Server

You restart the Policy Server for certain settings to take effect.

Follow these steps:

1. Open the Policy Server Management Console.
2. Click the Status tab, and click Stop in the Policy Server group box.

   The Policy Server stops as indicated by the red stoplight.

3. Click Start.

   The Policy Server starts as indicated by the green stoplight.

   Note: On UNIX or Linux operating environments, you can also execute the stop-all command followed by the start-all command to restart the Policy Server. These commands provide an alternative to the Policy Server Management Console.

Prepare for the Administrative UI Registration

You use the default CA SiteMinder® super user account (siteminder) to log into the Administrative UI for the first–time. The initial login requires that you to register the Administrative UI with a Policy Server, which creates a trusted relationship between both components.

You prepare for the registration by using the XPSRegClient utility to supply the super user account name and password. The Policy Server uses these credentials to verify that the registration request is valid and that the trusted relationship can be established.

Consider the following:

• The time from which you supply the credentials to when the initial Administrative UI login occurs is limited to 24 hours. If you do not plan on installing the Administrative UI within one day, complete the following before installing the Administrative UI.
• (UNIX) Be sure that the CA SiteMinder® environment variables are set before you use XPSRegClient. If the environment variables are not set, set them manually.

To prepare for the Administrative UI registration

1. Log into the Policy Server host system.
2. Run the following command:

   XPSRegClient siteminder[:passphrase] -adminui-setup -t timeout -r retries -c comment -cp -l log_path -e error_path -vT -vI -vW -vE -vF
   

   passphrase

   Specifies the password for the default CA SiteMinder® super user account (siteminder).

   Note: If you do not specify the passphrase, XPSRegClient prompts you to enter and confirm one.

   -adminui–setup

   Specifies that the Administrative UI is being registered with a Policy Server for the first–time.

   -t timeout

   (Optional) Specifies the allotted time from when you to install the Administrative UI to the time you log in and create a trusted relationship with a Policy Server. The Policy Server denies the registration request when the timeout value is exceeded.

   Unit of measurement: minutes

   Default: 240 (4 hours)

   Minimum Limit: 15

   Maximum Limit: 1440 (24 hours)

   -r retries

   (Optional) Specifies how many failed attempts are allowed when you are registering the Administrative UI. A failed attempt can result from submitting incorrect CA SiteMinder® administrator credentials when logging into the Administrative UI for the first–time

   Default: 1

   Maximum Limit: 5

   -c comment

   (Optional) Inserts the specified comments into the registration log file for informational purposes.

   Note: Surround comments with quotes.

   -cp

   (Optional) Specifies that registration log file can contain multiple lines of comments. The utility prompts for multiple lines of comments and inserts the specified comments into the registration log file for informational purposes.

   Note: Surround comments with quotes.

   -l log path

   (Optional) Specifies where the registration log file must be exported.

   Default: siteminder_home\log

   siteminder_home

   Specifies the Policy Server installation path.

   -e error_path

   (Optional) Sends exceptions to the specified path.

   Default: stderr

   -vT

   (Optional) Sets the verbosity level to TRACE.

   -vI

   (Optional) Sets the verbosity level to INFO.

   -vW

   (Optional) Sets the verbosity level to WARNING.

   -vE

   (Optional) Sets the verbosity level to ERROR.

   -vF

   (Optional) Sets the verbosity level to FATAL.

3. Press Enter.

   XPSRegClient supplies the Policy Server with the administrator credentials. The Policy Server uses these credentials to verify the registration request when you log into the Administrative UI for the first–time.