Support custom OIDC auth scenarios #111
Merged
Conversation
This file contains 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
feedmeapples
force-pushed
the
generic-auth-options
branch
2 times, most recently
from
8d17b6e to
0fc1ed1
Compare
feedmeapples
changed the title
feedmeapples
changed the title
feedmeapples
changed the title
feedmeapples
force-pushed
the
generic-auth-options
branch
from
0fc1ed1 to
bc9e6f8
Compare
GiantRobots
approved these changes
Mar 3, 2022
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.
What was changed
Allows to configure generic OIDC Auth options
Why?
Support for provider specific scenarios, such as Auth0 invitation flow
Checklist
Closes
How was this tested: