You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
we have certain scopes which the authorization server should only release to an OAuth2-client if the user has the right role for it.
e.g. scope "courses_read" may only be issued when the user has the student-role.
You could of course implement this check at the resources (courses API in case of my example), but I believe it's the responsibility of the authorization server. Resources could then solely base their authorizations based on the presence the "courses_read" scope in the token.
The text was updated successfully, but these errors were encountered:
This was considered a while ago in #351 but hasn't been implemented yet, to my knowledge. You'd need to hook into a few different places in the server to make it work. We'd be happy to take a pull request that made this a pluggable function.
Hi
we have certain scopes which the authorization server should only release to an OAuth2-client if the user has the right role for it.
e.g. scope "courses_read" may only be issued when the user has the student-role.
You could of course implement this check at the resources (courses API in case of my example), but I believe it's the responsibility of the authorization server. Resources could then solely base their authorizations based on the presence the "courses_read" scope in the token.
The text was updated successfully, but these errors were encountered: