-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Refreshing a token sending scopes separated by +
does not work
#1686
Comments
I am not a maintainer, but I do not think this would be possible to support since |
Fair enough. I think the issue here is inconsistency? I don’t have a |
Does that only happen in the authorization_code grant? I have done the following test in password grant:
|
Interesting question. I can’t test other grants right now but yours is helpful enough. |
I do not think this is a matter of consistency, when the client does the redirect they are url-encoding spaces to |
Steps to reproduce
Try to refresh a token sending the scope field with strings separated by
+
. The users of the API just tried to use the same format they used on issuing a token (authorization_code
grant).Expected behavior
It refreshes the access token like when sending scopes separated by space.
Actual behavior
It returns a 401 with:
System configuration
Doorkeeper initializer:
Ruby version:
2.6.10
Gemfile.lock:
Gemfile.lock content
The text was updated successfully, but these errors were encountered: