Merge lp:~matiasb/canonical-identity-provider/working-on-1192555 into lp:canonical-identity-provider/release
Proposed by
Matias Bordese
Status: | Merged |
---|---|
Approved by: | Matias Bordese |
Approved revision: | no longer in the source branch. |
Merged at revision: | 981 |
Proposed branch: | lp:~matiasb/canonical-identity-provider/working-on-1192555 |
Merge into: | lp:canonical-identity-provider/release |
Diff against target: |
89 lines (+56/-3) 2 files modified
src/webui/tests/test_views_ui.py (+47/-1) src/webui/views/ui.py (+9/-2) |
To merge this branch: | bzr merge lp:~matiasb/canonical-identity-provider/working-on-1192555 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ricardo Kirkner (community) | Approve | ||
Review via email: mp+176474@code.launchpad.net |
Commit message
Fixed reset password view to handle email in a case insensitive way.
Description of the change
Fixed reset password view to handle email in a case insensitive way.
Reset password tokens generated through the API v1.0 allow the creation of tokens with email with different cases (this does not affect API v2 because since ALLOW_UNVERIFIED is enabled for everyone, the preferred email is selected over the email in the token).
This also arises the question: should we normalize email addresses before saving to db (and before searching on db)? Right now emails are stored as passed by the user.
To post a comment you must log in.
LGTM