-
-
Notifications
You must be signed in to change notification settings - Fork 489
Avoid populating spurious token credentials #542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
"""Add attributes from an auth code response to self.""" | ||
|
||
if 'code' in response: | ||
self.code = response.get('code') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Initialize self.code
in __init__
?
@@ -168,5 +168,5 @@ def parse_request_uri_response(self, uri, state=None, scope=None): | |||
.. _`Section 3.3`: https://tools.ietf.org/html/rfc6749#section-3.3 | |||
""" | |||
self.token = parse_implicit_response(uri, state=state, scope=scope) | |||
self._populate_attributes(self.token) | |||
self._populate_token_attributes(self.token) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a test_populate_attributes
for mobile application?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is now! 👍
(cherry picked from commit 657065d)
This patch ensures we do not pick up client attributes too early.