You are viewing a plain text version of this content. The canonical link for it is here.

Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2018/07/17 05:07:00 UTC

[jira] [Created] (JAMES-2471) Changing a password should use latest configured hashing algorithm

Tellier Benoit created JAMES-2471:
-------------------------------------

             Summary: Changing a password should use latest configured hashing algorithm
                 Key: JAMES-2471
                 URL: https://issues.apache.org/jira/browse/JAMES-2471
             Project: James Server
          Issue Type: Improvement
          Components: CLI, UsersStore &amp; UsersRepository, webadmin
    Affects Versions: master
            Reporter: Tellier Benoit


James stores users passwords hashed in a database.

The hashing algorithm is being stored on a per-user basis. However, when changing a password, the password is hashed with the algorithm configured at user creation (not the one used during the update).

We would need, when updating user password, to ensure we are using the currently configured algorithm.

This has to be working using James WebAdmin and CLI



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org