Installation Guides › Policy Server Installation Guide › Installing the Policy Server on Windows Systems › Policy Server Configuration Wizard › How to Use the Configuration Wizard › Gather Information for the Configuration Wizard › Sun Java System Directory Server Information

Sun Java System Directory Server Information

You only have to gather Sun Java System Directory Server information if you plan on configuring a Sun Java System Directory Server as a policy store.

Gather the following required information to configure a Sun Java System Directory Server as a policy store. You can use the Sun Java System Directory Server Information Worksheet to record your values.

• System IP address—Determine the IP address of the system where the Sun Java Systems Directory Server is installed.
• Directory instance port number—Determine the port number for the Sun Java Systems Directory Server instance.

  Default: 389

• Root DN—Identify the root DN of the Sun Java System Directory Server.

  Example: o=yourorg.com

• Administrator account—Identify the user name (Bind DN) for the LDAP administrator account.

  Example: cn=Directory Manager

• Administrator password—Identify the password for the Sun Java System Directory Server administrator.
• Alternate LDAP administrator—By default, SOA Security Manager uses the LDAP administrator account to communicate with the LDAP server. You can, however, have the SOA Security Manager policy store administered through a different LDAP user account. Determine the complete administrator DN and password to configure SOA Security Manager in this way.

  Note: This user should have all of the necessary privileges to modify attributes and change passwords.

• SOA Security Manager Super User password—The predefined SOA Security Manager Super User account has maximum SOA Security Manager privileges. Determine the password for the SOA Security Manager Super User account.

  Limits: 6 to 24 alphanumeric characters.

  Note: We recommend that this account not be used for day-to-day operations. Rather, use the Super User account to access the FSS Administrative UI for the first time and create an administrator account with system configuration privileges.