docs: add Supabase as a supported CTS OIDC provider#20
Draft
coderdan wants to merge 1 commit into
Draft
Conversation
Add Supabase to the list of identity providers that can be configured for CTS federation, and replace the stale 'reach out to support' sentence with a pointer to self-service OIDC provider management in the CipherStash Dashboard.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Bringing your own Identity Provider).Context
CTS now supports Supabase as an OIDC provider alongside Auth0, Okta, and Clerk. The dashboard also offers self-service OIDC provider configuration under workspace settings, so the previous "contact support" instruction is no longer accurate.