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

onCredentials ext point #3634

Closed
hueniverse opened this issue Oct 22, 2017 · 1 comment
Closed

onCredentials ext point #3634

hueniverse opened this issue Oct 22, 2017 · 1 comment
Assignees
Labels
breaking changes Change that can breaking existing code feature New functionality or improvement
Milestone

Comments

@hueniverse
Copy link
Contributor

Breaking change: if the request has valid credentials but fails access (scope, entity), the request.auth.isAuthenticated property will be true. It will still fail and jump to response validation as before, but the flag will not be false as before. Adds a new request.isAuthorized flag which will be false.

@hueniverse hueniverse added breaking changes Change that can breaking existing code feature New functionality or improvement labels Oct 22, 2017
@hueniverse hueniverse added this to the 17.0.0 milestone Oct 22, 2017
@hueniverse hueniverse self-assigned this Oct 22, 2017
@lock
Copy link

lock bot commented Jan 9, 2020

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
breaking changes Change that can breaking existing code feature New functionality or improvement
Projects
None yet
Development

No branches or pull requests

1 participant