foousers { org.ldaptive.jaas.LdapLoginModule REQUIRED ldapUrl="ldap://ldap.example.com:389" baseDn="ou=foo,ou=dev,dc=example,dc=com" userFilter="(uid={user})" useStartTLS="false" useSSL="false" subtreeSearch="true" dnResolver="org.ldaptive.auth.PooledSearchDnResolver" authenticationHandler="org.ldaptive.auth.PooledBindAuthenticationHandler" cacheId="ldaptive-foouser-pool" debug="true";};
barusers {
org.ldaptive.jaas.LdapLoginModule REQUIRED ldapUrl="ldap://ldap.example.com:389" baseDn="ou=bar,ou=dev,dc=example,dc=com" userFilter="(uid={user})" useStartTLS="false" useSSL="false" subtreeSearch="true" dnResolver="org.ldaptive.auth.PooledSearchDnResolver" authenticationHandler="org.ldaptive.auth.PooledBindAuthenticationHandler" cacheId="ldaptive-barusers-pool" debug="true";
};
1. Does setting different pools for different configs helps in better performance or its recommended to have one config for all ?
2. adding the pooling properties(http://www.ldaptive.org/docs/guide/connections/pooling.html) nested in these config will have effect on the overall pooling ?
3. when adding no pooling parameters, does ldaptive try to validate the connections automatically ? if so what is the default interval 30 mins ?
On Sat, Oct 22, 2016 at 9:51 AM Kamesh Sampath <ksam...@redhat.com> wrote:1. Does setting different pools for different configs helps in better performance or its recommended to have one config for all ?The cache holds the entire Authenticator, not just the pool. So you must use different cacheIds for each config and consequently maintain separate pools.