feat: Add Keycloak Provider on signInWithIdToken #1068
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
dshukertjr
reviewed
Oct 21, 2024
|
Yes, I'll do that. |
|
done. :D |
dshukertjr
approved these changes
Oct 21, 2024
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 kind of change does this PR introduce?
Relate: #1045
Add Keycloak Provider on signInWithIdToken
What is the current behavior?
signInWithIdToken are only available for Google, Apple or Kakao
What is the new behavior?
Authorize Keycloak to use signInWithIdToken
Additional context
We need a transparent connection that uses the accessToken and idToken that provides us with keycloak authentication.
As the connection has already been established through our systems, we need to provide the authentication information to gotrue directly using the signInWithIdToken method.