Allow saving login-hint with client configuration. #5
Conversation
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
1 participant
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.
It would be very useful to be able to save a login_hint with the client configuration. Certain providers, such as Auth0, enable what they call Identifier-First authentication flows (https://auth0.com/docs/authenticate/login/auth0-universal-login/identifier-first). It piggy-backs of the OIDC standard
login_hintparameter. When testing such flows, setting thelogin_hintneeds to be set in order to avoid having to manually enter it on the provider's side. Allowing us to save the login_hint with client configuration would avoid having to continuously input this for every test.