directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lécharny (Jira) <>
Subject [jira] [Updated] (DIRSERVER-2281) We don't need anymore a credential cache
Date Thu, 19 Mar 2020 18:36:01 GMT


Emmanuel Lécharny updated DIRSERVER-2281:
    Fix Version/s:     (was: 2.0.0.AM26)

> We don't need anymore a credential cache
> ----------------------------------------
>                 Key: DIRSERVER-2281
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: authn
>    Affects Versions: 2.0.0.AM25
>            Reporter: Emmanuel Lécharny
>            Priority: Major
>             Fix For: 2.0.0.AM27
> Once upon a time, when we were authenticating users, we were fetching the password from
the backend, which was costly, beside checking that the entry existed (another lookup done
on the backend).
> The idea was to add a credential cache to avoid doing that repetitively.
> The thing is that it's not anymore necessary because before doing any kind of password
verification, we fetch the entire entry, including its password.
> Still, we have kept the credential cache.
> We can now remove it, which will incidentally remove a contention point (and the necessity
of invalidating the cache when the entry was moved, renamed, or its password removed or modified).
> An extra benefit is that we won't have a place in memory where the password will be stored
for a long period of time...

This message was sent by Atlassian Jira

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message