Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
Standalone LDAP registry wizard settings
Use this security wizard page to provide the basic settings to connect the application server to an existing LDAP registry.
To view this security wizard page, click Security > Global security > Security configuration wizard. We can modifythe LDAP registry configuration...
- Click Security > Global security.
- Under User account repository, click the Available realm definitions drop-down list, selectStandalone LDAP registry, and click Configure.
Primary administrative user name
Name of a user with administrative privileges that is defined in your user registry.
The user name is used to log onto the administrative console when administrative security is enabled. Versions 6.1 and later require an administrative user that is distinct from the server user identity so that administrative actions can be audited.
In WAS Version 6.0x, a single user identity is required for both administrative access and internal process communication. When you migrate to Version 7.0, this identity is used as the server user identity. You need to specify another user for the administrative user identity.
Type of LDAP server
Type of LDAP server to which you connect.
IBM SecureWay Directory Server is not supported.
Host
Host ID (IP address or DNS name) of the LDAP server.
Port
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 v6.1 configuration, and a WAS at Version 7.0 is going to interoperate with the v6.1 server, verify that port 389 is specified explicitly for the v7.0 server.
Default: 389 Type: Integer
Base distinguished name (DN)
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.
Bind distinguished name (DN)
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.
Bind password
Password for the application server to use when binding to the directory service.
Use specific directory servers as the LDAP server
Configure LDAP user registries
Related
Standalone LDAP registry settings