vbatts/quay
Archived
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Fix encrypted password generator to use the LDAP username, not the Quay username.

Browse source 
Currently, we use the Quay username via `verify_user` when we go to create the encrypted password. This is only correct if Quay has not generated its own different username for the LDAP user, and fails if it has. We therefore add a new method `confirm_existing_user`, which looks up the federated login for the LDAP user and then runs the auth flow using that username.
This commit is contained in:
Joseph Schorr 2015-05-20 16:37:09 -04:00
parent d5e70c6e2a
commit b0d763b5ff
4 changed files with 69 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

3
endpoints/api/user.py
View file

@ -370,8 +370,7 @@ class ClientKey(ApiResource):
""" Return's the user's private client key. """
username = get_authenticated_user().username
password = request.get_json()['password']
(result, error_message) = authentication.verify_user(username, password)
(result, error_message) = authentication.confirm_existing_user(username, password)
if not result:
raise request_error(message=error_message)