You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2007/03/09 15:18:24 UTC
[jira] Created: (DIRSERVER-870) Simplify the password cache
mechanism
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
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.
[jira] Assigned: (DIRSERVER-870) Simplify the password cache
mechanism
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (DIRSERVER-870) Simplify the password cache
mechanism
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-870.
-----------------------------------------
Resolution: Fixed
The cache has been re-enabled, using another mechanism (LRU).
> 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.
[jira] Closed: (DIRSERVER-870) Simplify the password cache
mechanism
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny closed DIRSERVER-870.
---------------------------------------
> 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.
[jira] Commented: (DIRSERVER-870) Simplify the password cache
mechanism
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479700 ]
Emmanuel Lecharny commented on DIRSERVER-870:
---------------------------------------------
Removed the cache in the SimpleAuthenticator, o avoid having potential pbs when a user modify his password. This should also fix issue DIRSERVER-872 (which was already fixed by Alex, by cache invalidation).
> 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.