Skip to content
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

Access Token Response does not include scope #22

Closed
bfxt opened this issue Jul 16, 2018 · 3 comments
Closed

Access Token Response does not include scope #22

bfxt opened this issue Jul 16, 2018 · 3 comments
Assignees

Comments

@bfxt
Copy link

bfxt commented Jul 16, 2018

RFC6749 section 5.1 says that Access Token Response should include the authorized scope when it does not match the requested one:

scope
OPTIONAL, if identical to the scope requested by the client;
otherwise, REQUIRED. The scope of the access token as
described by Section 3.3.

@leejo leejo self-assigned this Jul 16, 2018
@leejo
Copy link
Collaborator

leejo commented Jul 16, 2018

I thought we always returned this? I'll take a look.

@bfxt
Copy link
Author

bfxt commented Jul 16, 2018

Should easily be fixed by adding it to the "$json_response"-object in "sub _access_token_request". Thank you for looking into that. Might be faster than me trying to figure out how to contribute to this.

@leejo leejo closed this as completed in 1556899 Jun 18, 2020
@leejo
Copy link
Collaborator

leejo commented Jun 18, 2020

v0.46 on its way to CPAN

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants