Fix urldecoding of client_id/secret #60
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I read a bit of the RFC and it seems client_id/secret should be urlencoded (http://tools.ietf.org/html/rfc6749#section-2.3.1), so i tried this on my test system too:
And the django console still says:
But:
Now, this is the authentication method from oauth2_validators.py:
As you can see, the comment lies. Section 3.2.1 says authentication is done as specified in section 2.3.1, The code decodes the base 64 but then tries to fetch the application model without urldecoding the client id and secret. So I went ahead and added urlib.unquote_plus() to the decoding, and ta-da:
My debugger confirms this, I think this is a bug.