public final Class LdapPoolManager

Obtains a pooled connection that either already exists or is newly created using the parameters supplied. If it is newly created, it needs to go through the authentication checks to determine whether an LDAP bind is necessary. Caller needs to invoke ldapClient.authenticateCalled() to determine whether ldapClient.authenticate() needs to be invoked. Caller has that responsibility because caller needs to deal with the LDAP bind response, which might involve referrals, response controls, errors, etc. This method is responsible only for establishing the connection.

Returns:LdapClient

an LdapClient that is pooled.

Determines whether pooling is allowed given information on how the connection will be used. Non-configurable rejections: - nonstandard socketFactory has been specified: the pool manager cannot track input or parameters used by the socket factory and thus has no way of determining whether two connection requests are equivalent. Maybe in the future it might add a list of allowed socket factories to be configured - trace enabled (except when debugging) - for Digest authentication, if a callback handler has been specified: the pool manager cannot track input collected by the handler and thus has no way of determining whether two connection requests are equivalent. Maybe in the future it might add a list of allowed callback handlers. Configurable tests: - Pooling for the requested protocol (plain or ssl) is supported - Pooling for the requested authentication mechanism is supported