Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <2842333.1173471369546.JavaMail.jira@brutus>
Date: Fri, 9 Mar 2007 12:16:09 -0800 (PST)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Assigned: (DIRSERVER-870) Simplify the password cache
 mechanism
In-Reply-To: <7191114.1173449904240.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DIRSERVER-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny reassigned DIRSERVER-870:
-------------------------------------------

    Assignee: Emmanuel Lecharny

> Simplify the password cache mechanism
> -------------------------------------
>
>                 Key: DIRSERVER-870
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-870
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>         Assigned To: Emmanuel Lecharny
>            Priority: Minor
>
> We have at least two level of caches for user passwrds :
> - one is managed into the Authenticator
> - and we may also have a cache associated with the userPassword attributeTypes (if declared in the configuration)
> We could keep only one cache by simply removing the weak cache from the authenticator (this cache cannot be resized, its size is staically fixed to 1000 passwords).
> The main problem with this cache is that we have to update it when a user modify his password, when the standard cache is automatically updated. And from a philosophical point of view, doing the same thing at two different places is somehow a waste of time and error prone ...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.