Add action after_authenticate_success#175
Open
mikaelengstrom wants to merge 1 commit intopsignoret:masterfrom
Open
Add action after_authenticate_success#175mikaelengstrom wants to merge 1 commit intopsignoret:masterfrom
mikaelengstrom wants to merge 1 commit intopsignoret:masterfrom
Conversation
The hook fires after successful authentifications via Azure. It might be useful for various cases, but my primary motivation is to store additional Azure-data in user-meta on login
Author
|
@psignoret Do you have any thoughts on this? |
0320183 to
37c8428
Compare
Author
|
@psignoret – Could you please review this? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The hook fires after successful authentication via Azure.
Motivation
It might be useful for various cases, a developer might want to store additional Azure-data in user-meta on login. Or track info like "last login via AD" to be able to identified potentially 'dead' accounts. One might also want to set up more complex group/role-mapping rules then the plugin is capable of today
If we have this in place we could let advanced users put code like this in their application-code: