[jira] [Updated] (DIRSERVER-2179) Password hashing interceptor - password history entries are not hashed
[ https://issues.apache.org/jira/browse/DIRSERVER-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny updated DIRSERVER-2179: - Component/s: hash interceptor > 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: hash interceptor, 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: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSERVER-2179) Password hashing interceptor - password history entries are not hashed
[ https://issues.apache.org/jira/browse/DIRSERVER-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny updated DIRSERVER-2179: - Component/s: ppolicy > 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: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org