Add ability to define authorization callback #3777
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently our authentication simply authorizes users based on whether they have been given permissions in the OAuth provider configuration. Often times this is controlled by IT or is otherwise difficult to manage so its often easier to grant permissions to use the OAuth provider freely but then restrict usage in the application itself. If you want to do this you currently have to validate the
pn.state.user
orpn.state.user_info
yourself and then modify your application based on whether the user is authorized or not.To make this simpler we introduce a
pn.config.authorize_callback
which is given theuser_info
dictionary and returnsTrue
orFalse
depending on whether the user should be authorized.