Installation and Upgrade Guides › Policy Server Installation Guide › Configuring LDAP Directory Servers to Store CA SiteMinder® Data

Configuring LDAP Directory Servers to Store CA SiteMinder® Data

LDAP Directory Servers as a Policy or Key Store

The CA SiteMinder® policy store is the repository for all policy–related information. All Policy Servers in a CA SiteMinder® installation must share policy store data, either directly or through replication. CA SiteMinder® is installed with tools that let administrators move policy store data from one storage facility to another.

When you install the Policy Server, you can automatically configure one of the following directory servers as a policy store:

• Microsoft Active Directory Lightweight Directory Services (AD LDS)
• Oracle Directory Server (formerly Sun Java System Directory Server)

If you do not use the Policy Server to configure a policy store automatically, you can manually configure a policy store after installing the Policy Server. Additionally, after you install the Policy Server, you can use the Policy Server Management Console to point the Policy Server to an existing policy store.

Note: For a list of supported CA and third-party components, refer to the CA SiteMinder® 12.52 Platform Support Matrix on the Technical Support site.

More information:

Locate the Platform Support Matrix

Installation Road Map

The following diagram illustrates a sample CA SiteMinder® installation and lists the order in which you install and configure each component.

• A solid line surrounds the Policy Server, which is required before configuring a policy store. If a Policy Server is not part of your environment, install it before continuing.
• The dotted line surrounds the policy store. Configure this component now.

The following figure depicts a single policy/key store instance. Although not illustrated, your environment can use separate instances for individual policy and key stores.

Important Considerations

To avoid possible policy store corruption, ensure that the server on which the policy store will reside is configured to store objects in UTF-8 form. For more information on configuring your server to store objects in UTF-8 form, see the documentation for that server.

Default Policy Store Objects Consideration

When you configure a policy store, the following default policy store object files are available:

• smpolicy.xml
• smpolicy-secure.xml

Consider the following items when choosing a file to:

• Both files contain the default objects that the policy store requires.
  • If you use the Policy Server Configuration Wizard to configure the policy store automatically, the wizard only uses smpolicy.xml.
  • If you want to use smpolicy–secure.xml, configure the policy store manually.
• Both files provide default security settings. These settings are available in the default Agent Configuration Object (ACO) templates that are available in the Administrative UI.
• The smpolicy-secure file provides more restrictive default security settings.
• Choosing smpolicy does not limit you from using the more restrictive default security settings. You can modify the default ACO settings using the Administrative UI.

  Note: For more information, see the Policy Server Configuration Guide.

The following table summarizes the security settings for both files: