Installation Guides › Policy Server Installation Guide › Installing the Policy Server on UNIX Systems › How to Install the Policy Server › Gather Information for the Installer › ADAM and AD LDS Server Information

ADAM and AD LDS Server Information

If you are configuring Microsoft ADAM or AD LDS to function as a policy store gather the following required information:

• System IP address—Identify the IP address of the directory server host system.
• Port number—Identify the port number on which the directory server is listening.
• Root DN of the application partition—Identify the root DN location of the application partition in the directory server where the policy store schema data must be installed.

  Example: dc=ca,dc=com

• Administrator domain name—Identify the full domain name, including the guid value, of the directory administrator.

  Example: CN=user1,CN=people,CN=Configuration,CN=guid

• Administrator password—Identify the password of the directory administrator.
• Alternate user account—By default, SOA Security Manager uses the administrator account to communicate with the directory server. However, you can use a different user account to administer the policy store. Identify the complete administrator DN and password to configure SOA Security Manager to use an alternative user account to administer the policy store.

  Note: This user must have the necessary permissions to modify attributes and change passwords.

• SOA Security Manager super user password—The default SOA Security Manager super user account (siteminder) has maximum permissions. Determine the password for the default super user account.

  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: We recommend that you do not use the default super user for day-to-day operations. Rather, use the default super user to access the FSS Administrative UI and Administrative UI for the first–time and then create an administrator with super user permissions.

More information:

Microsoft ADAM/AD LDS Information Worksheet