Add Zitadel Provider #1836
Open
Add Zitadel Provider #1836
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
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?
Add Zitadel Provider
What is the current behavior?
Currently, Supabase Auth does not support Zitadel as an authentication provider.
What is the new behavior?
With this PR, Zitadel will be available as a provider for authentication, allowing users to authenticate via Zitadel's OpenID Connect (OIDC) implementation.
Additional context
This implementation will enhance the flexibility of authentication methods available in Supabase, catering to applications using Zitadel for identity management.