Use this security wizard page to provide the basic settings to connect the application server to an existing Lightweight Directory Access Protocol (LDAP) registry. To view this security wizard page, click Security > Secure administration, applications, and infrastructure > Security configuration wizard. You can modify your LDAP registry configuration by completing the following steps:
Specifies the name of a user with administrative privileges that is defined in your custom user registry. The user name is used to log onto the administrative console when administrative security is enabled. V6.1 requires an administrative user that is distinct from the server user identity so that administrative actions can be audited. Attention: In WebSphere Application Server, Versions 5.x and 6.0.x, a single user identity is required for both administrative access and internal process communication. When migrating to V6.1, this identity is used as the server user identity. You need to specify another user for the administrative user identity.
Timeype of LDAP server to which you connect.
IBM SecureWay Directory Server is not supported.
Specifies the host ID (IP address or domain name service (DNS) name) of the LDAP server.
Specifies the host port of the LDAP server. If multiple application servers are installed and configured to run in the same single sign-on domain or if the application server interoperates with a previous version, it is important that the port number match all configurations. For example, if the LDAP port is explicitly specified as 389 in a V4.0.x configuration, and a WebSphere Application Server at V5 is going to interoperate with the V4.0.x server, verify that port 389 is specified explicitly for the V5 server.
| Default: | 389 |
| Type: | Integer |
Specifies the base distinguished name (DN) of the directory service, which indicates the starting point for LDAP searches of the directory service. In most cases, bind DN and bind password are needed. However, when anonymous bind can satisfy all of the required functions, bind DN and bind password are not needed.
For example, for a user with a DN of cn=John Doe , ou=Rochester, o=IBM, c=US, specify the Base DN as any of the following options: ou=Rochester, o=IBM, c=US or o=IBM, c=US or c=US. For authorization purposes, this field is case sensitive. This specification implies that if a token is received, for example, from another cell or Lotus Domino, the base DN in the server must match the base DN from the other cell or Lotus Domino server exactly.
If you need to interoperate between the application server V5 and a V5.0.1 or later server, enter a normalized base DN. A normalized base DN does not contain spaces before or after commas and equal symbols. An example of a non-normalized base DN is o = ibm, c = us or o=ibm, c=us. An example of a normalized base DN is o=ibm,c=us. In WebSphere Application Server, V5.0.1 or later, the normalization occurs automatically during run time.
Specifies the DN for the application server to use when binding to the directory service.
If no name is specified, the application server binds anonymously. See the Base distinguished name (DN) field description for examples of distinguished names.
Password for the application server to use when binding to the directory service.