[
https://issues.apache.org/jira/browse/DIRSERVER-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873285#comment-16873285
]
Emmanuel Lecharny commented on DIRSERVER-2179:
----------------------------------------------
The {{PasswordHashing}} interceptor is injected after the {{Authentication}}
interceptor, where the password history is created and injected into the entry
through the {{pwdHistory}} attribute.
That means we must process the {{pwdHistory}} attribute in the interceptor in
order to have the passwords stored hashed.
> Password hashing interceptor - password history entries are not hashed
> ----------------------------------------------------------------------
>
> Key: DIRSERVER-2179
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2179
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: ppolicy
> Reporter: Dmitry Smeliansky
> Priority: Major
>
> Hi.
> In order to use the server-side password policy validation - we have to pass
> the passwords as plaintext and not hashed by the client.
> Password hashing interceptor hashes the passwords according to the
> configuration, BUT - the new added pwdHistory entry will contain the
> plaintext value of the password.
> Is there any way to have the password policy validation on the server and the
> hashed password to be saved in the history at the same time?
> Thanks
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
