Configure an IBM Security Directory Suite as a Policy Store

1
casso10
1
Directory Server component of IBM Security Directory Suite 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 instructions on how to configure a single directory server instance to store policy data and encryption keys. You can configure a separate key store according to your implementation requirements.
Ensure that you have updated the expired default certificates on SDS virtual instance; otherwise, instances will run in configOnly mode, which does not support all required features. Follow this link for detailed steps.
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 upfront.
  • 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
Create a Directory Entry and Root Nodes
Use the IBM Security Directory Suite Web Administration Tool to create a directory entry and root nodes.
Note:
If applicable, create or load a server suffix using the IBM Security Directory Suite Configuration Tool.
Follow these steps:
  1. Create a directory entry for the root DN of the policy server data.
    ou=Nete
    command : idscfgsuf -I <instance_name> -s ou=Nete
  2. Create the following root nodes under the root DN:
    ou=Netegrity,ou=SiteMinder,ou=PolicySvr4,ou=XPS
    You can use
    idscfgsuf
    command or use IBM Directory Suite WebadminUI for this.
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.
    On 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 your CA Single Sign-On 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
    • Root 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. Select the following value from the Database list:
    Key Store
  9. Select the following value from the Storage list:
    LDAP
  10. Select the following option:
    Use Policy Store database
  11. Click OK.
Create the Policy Store Schema
Create the policy store schema so the directory server can function as a policy store and store objects.
Follow these steps:
  1. Access the directory server using the IBM Security Directory Suite virtual appliance console.
  2. Navigate to
    policy_server_home\
    IBMDirectoryServer.
    • policy_server_home
      Specifies the Policy Server installation path.
  3. Use the IBM Security Directory Suite virtual appliance console to add the
    V3.siteminderrelease
    schema file to the
    Configure, Advanced Configuration, Custom File Management, CustomIn
    section and run the following command.
    idscfgsch -I <instance_name> -s <configfilename>
    • release
      Specifies the CA Single Sign-On release.
  4. Navigate to
    policy_server_home
    \xps\db.
  5. Locate the following file:
    IBMDirectoryServer.ldif
  6. Use the IBM Security Directory Suite virtual appliance console to add the file to the
    Configure, Advanced Configuration, Custom File Management, CustomIn
    section and run the following command.
    idscfgsch -I <instance_name> -s <configfilename>
  7. Restart the directory server.
    The policy store schema is created.
Set the CA Single Sign-On Super User Password
The default CA Single Sign-On administrator account is named
siteminder
. The account has maximum permissions.
Do not use the default
super user
account for day-to-day operations. Use the default
super user
account to:
  • Access the Administrative UI for the first time.
  • Manage CA Single Sign-On utilities for the first time.
  • Create another administrator with super user 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 administrator.
    The password has the following requirements:
    • The password must contain at least six (6) characters and cannot exceed 24 characters.
    • The password cannot include an ampersand (&) or an asterisk (*) character.
    • 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 administrator account is set.
Import the Policy Store Data Definitions
Importing the policy store data definitions defines the types of objects that can be created and stored in the policy store.
Follow these steps:
  1. Open a command window and navigate to
    siteminder_home
    \xps\dd.
    • siteminder_home
      Specifies the Policy Server installation path.
  2. Run the following command:
    XPSDDInstall SmMaster.xdd
    • XPSDDInstall
      Imports the required data definitions.
Import the Default Policy Store Objects
Importing the default policy store objects configures the policy store for use with the Administrative UI and the Policy Server.
Consider the following items:
  • Ensure that you have write access to
    siteminder_home
    \bin. The import utility requires this permission to import the policy store objects.
    • siteminder_home
      Specifies the Policy Server installation path.
  • Before running a CA Single Sign-On utility or executable on Windows Server 2008, 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 your CA Single Sign-On component.
Follow these steps:
  1. Open a command window and navigate to
    siteminder_home
    \db.
  2. 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
      • npass
        Specifies that no passphrase is required. The default policy store objects do not contain encrypted data.
      Both files include the default policy store objects. These objects include the default security settings in the default Agent Configuration Object (ACO) templates. The smpolicy–secure file provides more restrictive security settings. For more information, see Default Policy Store Objects Consideration.
    • 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
  3. The policy store objects are imported.
    Note:
    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 later functionality, contact your CA account representative for licensing information.
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. Perform one of the following steps:
    On Windows:
    Leave all the check boxes in the first screen of the wizard cleared and click Next.
    On Linux:
    Type 5 and press Enter.
  3. 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.
  4. Complete the rest of the Policy Server configuration wizard.
    The Advanced Authentication Server is enabled.
Restart the Policy Server
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, execute the
    stop-ps
    and
    start-ps
    commands to restart Policy Server. To restart Policy Server and CA Risk Authentication, execute the
    stop-all
    and
    start-all
    commands.
Prepare for the Administrative UI Registration
Use the default 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.
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) Ensure that the CA Single Sign-On environment variables are set before you use XPSRegClient. If the environment variables are not set, set them manually.
Follow these steps:
  1. Log in to 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 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:
      15
      Maximum:
      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 administrator credentials when logging in to the Administrative UI for the first time.
      Default:
      1
      Maximum:
      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 in to the Administrative UI for the first time.