Digging deeper I've found that setting a CacheManager will result in afterAuthorizationCacheSet() being called. But, nothing about this is mentioned in the javadoc for AbstractLdapRealm. Is a subclass (of AbstractLdapRealm) required to use a CacheManager?
/Anders Anders Hammar wrote: > > Hi, > > I have a problem extending the AbstractLdapRealm class for > authentication. It's my understanding based on reading the javadoc > that a default implementation of LdapContextFactory > (DefaultLdapContextFactory) is being used if I don't change the > default behavior. However, when implementing a subclass of > AbstractLdapRealm for authentication (implementing the > queryForAuthenticationInfo method) the LdapContextFactory being passed > in is null. Checking the source, it seems as DefaultLdapContextFactory > is set when afterAuthorizationCacheSet() is called. > Who is responsible for calling afterAuthorizationCacheSet()? Should > the application using JSecurity do that? Or should my subclass do > that? > > Regards, > /Anders > > -- View this message in context: http://n2.nabble.com/AbstractLdapRealm-and-the-LdapContextFactory-tp1340535p1340966.html Sent from the JSecurity User mailing list archive at Nabble.com.
