Installation and Upgrade Guides › Directory Configuration Guide › Critical Path inJoin Directory Server v4.2 › Configure an inJoin Directory Server as a Policy Store

Configure an inJoin Directory Server as a Policy Store

You can configure a Critical Path inJoin Directory Server (IDS) as a policy store using the Critical Path's iCon GUI.

To configure a Critical Path inJoin Directory Server (IDS) as a policy store

1. Start the DSA.
2. Navigate to policy_server_home\bin on the machine where the Policy Server is installed.
   • policy_server_home

     Specifies the Policy Server installation path.

3. Run the following command:

   ldapmodify -hhost -pport -dAdminDN -wAdminPW -c
   -fdir_config_home\criticalpath\IDS_Add_Schema_R12sp2.ldif
   

   • -h host

     Specifies the IP address of the LDAP server.

   • -p port

     Specifies the port number of the LDAP server.

   • -d AdminDN

     Specifies the name of an LDAP user with privileges to create a new LDAP schema on the LDAP directory server.

     Example: cn=manager

   • -w AdminPW

     Specifies the password of the LDAP user with privileges to create a new LDAP schema on the LDAP directory server.

   • -c

     Specifies continuous mode (do not stop on errors).

   • -f

     Specifies the path and name of the schema file that is supplied with r12.0 SP2.

   • dir_config_home

     Specifies the Directory Configuration installation path.

   Note: ldapmodify requires version 4.2 of the Critical Path inJoin Directory Server.

4. Reload the schema, or verify that the schema has been updated.
5. Run the following command:

   ldapmodify -hhost -pport -dAdminDN -wAdminPW -c
   -fdir_config_home\xps\criticalpath\CriticalPath.ldif
   

   • -f

     Specifies the path and name of the XPS schema file that is supplied with r12.0 SP2.

6. Reload the schema, or verify that the schema has been updated.
7. Go to dsa, comms, LDAP, change the "paging mode" option to "always", and restart the DSA.

   The policy store schema is created for r12.0 SP2.

8. Manually create the following root nodes using Critical Path's iCon DIT administrator interface:
   • ou=Netegrity
   • ou=SiteMinder
   • ou=PolicySvr4
9. Run the following command:

   smobjimport -ipolicy_server_home/db/smdif/smpolicy.smdif -v
   

   • -i

     Specifies the path and name of the import file.

   • -v

     Turns on tracing and outputs error, warning, and comment messages.

   The base policy store data is imported from the file smpolicy.smdif.

10. Run the following command:

    smobjimport -ipolicy_server_home\db\smdif\ampolicy.smdif
    -dsiteminder_super_user_name -wsiteminder_super_user_password -f -v -l -c
    

    • -i

      Specifies the path and name of the import file.

    • -dsiteminder_super_user_name

      Specifies the name of the SiteMinder Super User account.

    • -wsiteminder_super_user_password

      Specifies the password for the SiteMinder Super User account.

    • -f

      Overrides duplicate objects

    • -v

      Turns on tracing and outputs error, warning, and comment messages in verbose format so that you can monitor the status of the import.

      Default value: stdout

    • -l

      Creates a log file.

    • -c

      Indicates that the smdif input file contains unencrypted data.

    smobjimport imports the policy store objects. These objects are automatically imported to the appropriate locations.

    Note: Importing ampolicy.smdif makes available Federation Security Services, Web Service Variables, and eTelligent Rules functionality that is separately licensed from SiteMinder. If you intend on using the latter functionality, contact your CA account representative for more information on licensing.

    The Critical Path inJoin Directory Server (IDS) is configured as a policy store.

Note: You can now import the policy store data definitions.