Configuring LDAP for user authentication
You can configure messaging users and groups by using an LDAP server. You can configure the LDAP server either by using the Amlen WebUI, or by using REST Administration APIs.
Messaging users send and receive messages. Messaging users are used in connection policies, messaging policies, and security policies when you filter access by user ID. Messaging groups are collections of messaging users. Messaging groups are also used in connection policies, messaging policies, and security policies when you filter access by group name. For more information about messaging users and groups, see Messaging users and groups.
If you have an existing LDAP server of users and groups, you can use the server to provide the messaging user and group information. You can only use one LDAP server for your messaging users and groups.
You can configure only one LDAP server. You might need to add a DNS entry to resolve the IP address of the LDAP server. Eclipse Amlen supports the following external LDAP servers: openLDAP, IBM Security Directory Server, and Microsoft Active Directory.
-
- URL
- The URL to connect to the LDAP server.
-
- Maximum connections
- The maximum number of concurrent connections that can be made to the LDAP server.
-
- Base DN
- The base distinguished name of the directory service.
-
- Bind DN
- The distinguished name to use when you bind to LDAP.
-
- Bind password
- The password to use when you bind to LDAP.
-
- Ignore case
- Whether to ignore case during an LDAP search.
-
- User suffix
- The distinguished name that is the suffix of the user distinguished name.
-
- Group suffix
- The distinguished name that is the suffix of the group distinguished name.
-
- User ID map
- The LDAP filter that maps the short name of a user to an LDAP entry.
-
- Group ID map
- The LDAP filter that maps the short name of a group to an LDAP entry.
-
- Group member ID map
- The LDAP filter that identifies user-to-group relationships.
-
- Timeout
- The timeout for LDAP calls, in seconds.
-
- Enable cache
- Whether credentials are cached.
-
- Cache Timeout
- The time to live of the authentication token, in seconds. After a user is authenticated, an authentication token is created for each user. This token is cached. If the cached token is not expired, then this token is used for authentication. If the cached token is expired, the user is authenticated against the configured LDAP server.
-
- Group Cache Timeout
- The group cache time to live, in seconds.
-
- Nested Group Search
- Whether to use nested group searching to find the group membership of a user.
-
- Certificate
- The certificate that is used to verify the LDAP server, if the LDAP URL uses TLS.
- Check Server Certificate
- Available in version 5.0.0.2 and later releases. Possible options are as follows:
- Use messaging server trust store
- When connecting to the LDAP server, the certificate that is presented by the server is checked using the certificate that is uploaded to the product trust store.
- Use public trust store
- The certificate that is presented by the LDAP server is checked against the public certificates that are installed as part of the operating system.
- Disable certificate verification
- No certificate verification is performed when connecting to the LDAP server. This is an insecure option that is designed for testing purposes only.
If you are updating an LDAP certificate in a High Availability (HA) environment, you must upload the new certificate on the primary server and then replicate this certificate on the standby server.
For more information about how to update certificates in an HA environment, see Updating a certificate for an LDAP connection in a High Availability environment by using REST Administration APIs.
For more information about configuring an LDAP server connection by using the Amlen WebUI, see Configuring an LDAP server by using the Amlen WebUI.
For more information about configuring an LDAP server connection by using REST Administration APIs, see Configuring an LDAP server by using REST Administration APIs.