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

Client scope permissions are not checked as expected on version 2.0.0-rc3-final #682

Closed
nurhat opened this Issue Oct 23, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@nurhat

nurhat commented Oct 23, 2018

Hi,

With password grant type, clients can request any registered scope even if the permission for the scope is not given. Is it an issue with the release or sth else. When I investigate the part of code , it seems it should work as expected.

Thx.
Nurhat

@PinpointTownes PinpointTownes added this to the 2.0.0 milestone Oct 23, 2018

@PinpointTownes PinpointTownes self-assigned this Oct 23, 2018

@PinpointTownes

This comment has been minimized.

Contributor

PinpointTownes commented Oct 23, 2018

Hey,

Thanks for reporting this security issue, which causes scope permissions to be ignored for public clients (confidential clients are not impacted).

I'll take care of fixing it and make sure it's included in the RTM release.

Thanks!

@PinpointTownes

This comment has been minimized.

Contributor

PinpointTownes commented Oct 23, 2018

Fixed by e7c4942.

New nightly builds should be pushed to MyGet.org within in the next minutes.

Thanks again for reporting it 👍

@nurhat

This comment has been minimized.

nurhat commented Oct 24, 2018

Thank you for the quick fix, when it will be released on nuget.org?

@nurhat nurhat closed this Oct 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment