-
Type:
Bug
-
Status: CLOSED
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.5.0
-
Component/s: User service (Pre-K1/2.6)
-
Labels:None
There are 3 problems with the current user 2.5.0 setup:
1) the authn cache uses a syncronized map so it is not centrally
controllable or configurable and perfomance in many threads would be
poor
- this can be switched over to use a central cache
2) the authn cache only takes effect if using webdav or logging in via
the login tool - JCR and other things that call the authenticate
method in UDS would not benefit from the caching - this can be fixed by forcing the authenticate method to call
through the cached authentication mechanism
3) some of the UDS methods make repeated calls to the provider before
the cache is checked, in my testing it looks like 3 calls go to the
provider for every user that is looked up for the first time, after
the first lookup the cache is used correctly - this can be fixed by simply correcting the methods which are making
the extra calls to the provider to use the cache instead
- relates to
-
SAK-13404 Jackrabbit should authenticate using the AuthenticationManager so calls are cached
-
- CLOSED
-
-
SAK-39055 org.sakaiproject.user.impl.test.AuthenticationCacheTest is failing
-
- CLOSED
-
-
SAK-9983 Give DAV-enabled sites a way to cache successful authentications
-
- CLOSED
-
-
SAK-10227 modify KerberosUserDirectoryProvider to use centralized authentication caching
-
- CLOSED
-
-
SAK-11498 Replace JLDAPDirectoryProvider internal cache with a centrally-managed cache
-
- CLOSED
-
- mentioned in
-
Page Loading...