Authenticating to GroupWise with Passwords Stored in an LDAP Directory

Enabling LDAP authentication for the POA is independent of these LDAP address book features. You need to enable LDAP authentication when you want the POA to authenticate the user's password in an LDAP directory rather than looking for a password in the user's GroupWise account information. The POA can make use of the following LDAP capabilities:

When you understand these LDAP capabilities, you are ready to set up LDAP authentication for your GroupWise users. See Providing LDAP Authentication for GroupWise Users.

Access Method

On a server-by-server basis (ConsoleOne > GroupWise System Operations > LDAP Servers), you can specify whether you want each LDAP server to respond to authentication requests using a bind or a compare.

Regardless of whether the POA is submitting bind requests or compare requests to authenticate GroupWise users, the POA can stay connected to the LDAP server as long as authentication requests continue to occur before the connection times out. This provides quick response as users are accessing their mailboxes.

LDAP Username

On a post office-by-post office basis (ConsoleOne > Post Office object > GroupWise tab > Security page), you can decide what username you want the POA to use when accessing the LDAP server.