-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR13
In case when cache is used for legacy LDAP security realm and any access to secured resource occures, then entry is added into cache even if user has not been authenticated correctly.
Note, in reproducer there is cache-failures=false
"cache-failures - This is a boolean that enables/disables the caching of failed searches. This has the potential for preventing an LDAP server from being repeatedly access by the same failed search, but it also has the potential to fill up the cache with searches for users that do not exist. This setting is particularly important for the authentication cache. " [1]
And even with cache-failures = false , non existing user "takes slot" in cache, thus this
- effectively could make cache smaller, because valid entries could be evicted due to max-cache-size.
- reduce benefit of LDAP cache and impacts performance in unpredictable manner.
Same behavior can be seen in 7.0.0.GA.
- is cloned by
-
JBEAP-11350 (7.0.z) Legacy ldap realm, entry for non existing user are cached
- Resolved
-
WFCORE-2502 Legacy ldap realm, entry for non existing user are cached
- Resolved
-
JBEAP-9542 Legacy ldap realm, entry for non existing user are cached
- Closed
- is incorporated by
-
JBEAP-11466 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta28
- Closed