Configure an Oracle Internet Directory Server as a Policy Store
Contents
casso126
Contents
2
Oracle Internet Directory (OID) 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. The following sections provide instruction on how to configure a single directory server instance to store policy data and encryption keys. If your implementation requires, you can configure a separate key store.
Gather Directory Server Information
casso126
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.
- Host informationSpecifies 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 DNSpecifies 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 passwordSpecifies the password for the Administrative DN.
- Policy store root DNSpecifies the distinguished name of the node in the LDAP tree where policy store objects are to be defined.
- SSL client certificateSpecifies the pathname of the directory where the SSL client certificate database file resides.Limit:SSL only
Index a Required Attribute
Indexing the following attribute prevents an error from occurring when you import the default policy store objects:
modifyTimestamp
Follow these steps:
- Log in to the Oracle Internet Directory host system.
- Use the Oracle catalog command line tool to run the following command:oracle_home/ldap/bin/catalog connect=conn_stradd=TRUE attribute=modifyTimestamp
- oracle_homeSpecifies the Oracle Internet Directory installation path.
- conn_strSpecifies the directory database connect string. If you have configured a tnsnames.ora file, then enter the net service name specified in the file.
For more information about the catalog command line tool, see the Oracle documentation.
Configure a Domain in Oracle Internet Directory
To configure an OID as a policy store, first create a domain in OID.
Follow these steps:
- Open Oracle Data Manager (ODM).
- Right-click Entry Management, and select Create.
- Enterdc=dcbokfor the Distinguished Name value.
- Enterdcfor the dc value.
- Create an organizational unit.
- Select an organizational unit.
- Enterou=bok,dc=dcbokfor the Distinguished Name value.
- Enterbokfor the ou value.The OID domain is configured.
Point the Policy Server to the Policy Store
casso126
You point the Policy Server to the policy store so the Policy Server can access the policy store.
Follow these steps:
- Open the Policy Server Management Console.casso126On Windows Server, if User Account Control (UAC) is enabled 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 yourCA Single Sign-Oncomponent.
- Click the Data tab.
- Select the following value from the Database list:Policy Store
- Select the following value from the Storage list:LDAP
- Configure the following settings in the LDAP Policy Store group box.
- LDAP IP Address
- Admin Username
- Password
- Confirm Password
- Root DN
You can click Help for a description of fields, controls, and their respective requirements. - Click Apply.
- Click Test LDAP Connection to verify that the Policy Server can access the policy store.
- Select the following value from the Database list:Key Store
- Select the following value from the Storage list:LDAP
- Select the following option:Use Policy Store database
- Click OK.
Create the Policy Store Schema
You create the policy store schema so the directory server can function as a policy store and store
CA Single Sign-On
objects.Follow these steps:
- Run the following command:smldapsetup ldgen -ffile_name.ldif
- -ffile_nameSpecifies the name of the schema file that you are creating.
- Run the following command:smldapsetup ldmod -ffile_name.ldif
- -ffile_nameSpecifies the name of the schema file that you created.
- Run the following command:ldapmodify -hhost-pport-DAdminDN-wAdminPW-c -fsiteminder_home/xps/db/OID_10g.ldif-Z -PcertAlthough the schema file is version–specific, you can use this file to import the policy store schema for all supported versions of OID.
- -hhostSpecifies the IP address of the LDAP directory server.Example: 123.123.12.12
- -pportSpecifies the port number of the LDAP directory server.Example:3500
- -DAdminDNSpecifies the name of the LDAP user who has the privileges to create schema in the LDAP directory server.
- -wAdminPWSpecifies the password of the administrator specified by the -d option.
- -cSpecifies continuous mode (do not stop on errors).
- -fsiteminder_homeSpecifies the Policy Server installation path.
- -Z(Optional) Specifies an SSL-encrypted connection.
- -Pcert(Optional) Specifies the path of the SSL client certificate database file (cert8.db).Example:If cert8.db exists in app/siteminder/ssl, specify:-Papp/siteminder/ssl
Set the
CA Single Sign-On
Super User Passwordcasso126
The default administrator account is named
siteminder
. The account has maximum permissions.Do not use the default super user for day-to-day operations. Use the default super user to:
- Access the Administrative UI for the first time.
- ManageCA Single Sign-Onutilities for the first time.
- Create another administrator with super user permissions.
Follow these steps:
- Copy the smreg utility tositeminder_home\bin.
- siteminder_homeSpecifies the Policy Server installation path.
The utility is at the top level of the Policy Server installation kit. - Run the following command:smreg -supassword
- passwordSpecifies the password for the default administrator.
- 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.
If you are configuring an Oracle policy store, the password is case–sensitive. The password is not case–sensitive for all other policy stores. - Delete smreg fromsiteminder_home\bin. Deleting smreg prevents someone from changing the password without knowing the previous one.
The password for the default administrator account is set.
Import the Policy Store Data Definitions
casso126
Importing the policy store data definitions defines the types of objects that can be created and stored in the policy store.
Follow these steps:
- Open a command window and navigate tositeminder_home\xps\dd.
- siteminder_homeSpecifies the Policy Server installation path.
- Run the following command:XPSDDInstall SmMaster.xdd
- XPSDDInstallImports the required data definitions.
Import the Default Policy Store Objects
casso126
Importing the default policy store objects configures the policy store for use with the Administrative UI and the Policy Server.
Consider the following items:
- Be sure that you have write access tositeminder_home\bin. The import utility requires this permission to import the policy store objects.
- siteminder_homeSpecifies the Policy Server installation path.
- If Windows User Account Control (UAC) is enabled, open the command-line window with administrator permissions. Open the command-line window this way, even if your account has administrator privileges. For more information, see the release notes for yourCA Single Sign-Oncomponent.
Follow these steps:
- Open a command window and navigate tositeminder_home\db.
- Import one of the following files:
- To import smpolicy.xml, run the following command:XPSImport smpolicy.xml -npass
- To import smpolicy–secure.xml, run the following command:XPSImport smpolicy-secure.xml -npass
- npassSpecifies that no passphrase is required. The default policy store objects do not contain encrypted data.
- To import Option Pack functionality, run the following command:XPSImport ampolicy.xml -npass
- To import federation functionality, run the following command:XPSImport fedpolicy-12.5.xml -npass
Importing ampolicy.xml makes available legacy federation and Web Service Variables functionality that is separately licensed from
CA Single Sign-On
. If you intend on using the latter functionality, contact your CA account representative for licensing information.Restart the Policy Server
casso126
You restart the Policy Server for certain settings to take effect.
Follow these steps:
- Open the Policy Server Management Console.
- Click the Status tab, and click Stop in the Policy Server group box.The Policy Server stops as indicated by the red stoplight.
- Click Start.The Policy Server starts as indicated by the green stoplight.Note: To restart the Policy Server on UNIX, execute either thestop-psandstart-pscommands orstop-allandstart-allcommands.
Prepare for the Administrative UI Registration
casso126
You use the default super user account 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 items:
- 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 steps before installing the Administrative UI.
- (UNIX) Be sure that theCA Single Sign-Onenvironment variables are set before you use XPSRegClient. If the environment variables are not set, set them manually.
Follow these steps:
- Log in to the Policy Server host system.
- Run the following command:XPSRegClient super_user_account_name[:passphrase] -adminui-setup -ttimeout-rretries-ccomment-cp -llog_path-eerror_path-vT -vI -vW -vE -vF
- passphraseSpecifies the password for the default super user account.If you do not specify the passphrase, XPSRegClient prompts you to enter and confirm one.
- -adminui–setupSpecifies that the Administrative UI is being registered with a Policy Server for the first–time.
- -ttimeout(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:minutesDefault:240 (4 hours)Minimum:15Maximum:1440 (24 hours)
- -rretries(Optional) Specifies how many failed attempts are allowed when you are registering the Administrative UI. A failed attempt can result from submitting incorrect administrator credentials when logging in to the Administrative UI for the first time.Default:1Maximum:5
- -ccomment(Optional) Inserts the specified comments into the registration log file for informational purposes.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.Surround comments with quotes.
- -llog_path(Optional) Specifies where the registration log file must be exported.Default:siteminder_home\logsiteminder_homeSpecifies the Policy Server installation path.
- -eerror_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.
- 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 in to the Administrative UI for the first time.