-
Notifications
You must be signed in to change notification settings - Fork 517
feat: add support for managing SSO providers by resource_id #2081
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
- Updated API for SSO providers to allow get, put, delete by `resource_id` - Extended `loadSSOProvider` to lookup by either `idp_id` or `resource_id` - Added optional `resource_id` field to `SSOProvider` model - Implemented `FindSSOProviderByResourceID` in model layer - Renamed `FindAllSAMLProviders` to `FindAllSSOProviders` - Included pagination & filtering support in and `FindSSOProviderByFilter` - Note: this is not currently being used, waiting to hear teams feedback - Included full E2E test coverage for the new `/resources/{resource_id}` admin endpoints.
…efix This change simplifies self-service SSO flows by enabling lookup of SSO providers via a `resource_id`, which maps to an infrastructure org ID. This removes the need for syncing external mappings. Key changes: - Extended `loadSSOProvider` to accept `resource_`-prefixed `idp_id` values - Removed previously introduced `/resources` routes - Added filtering to the `/admin/sso/providers` via `?resource_id{,_prefix}=` - Reworked `FindAllSSOProvidersByFilter` to drop pagination/sorting - Updated E2E test suite for full SSO coverage
Pull Request Test Coverage Report for Build 16380883473Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
The sso_providers.disabled column was added to the SSOProvider.
hf
approved these changes
Jul 19, 2025
cemalkilic
pushed a commit
that referenced
this pull request
Aug 6, 2025
🤖 I have created a release *beep* *boop* --- ## [2.178.0](v2.177.0...v2.178.0) (2025-08-05) ### Features * add sign in with ethereum ([#2069](#2069)) ([079b242](079b242)) * add support for managing SSO providers by resource_id ([#2081](#2081)) ([5ca4489](5ca4489)) * log all audit events separately to prevent missing events ([#2086](#2086)) ([3b666f5](3b666f5)) * skip nonce check for Facebook Limited Login auth ([#2082](#2082)) ([f1b15ff](f1b15ff)) * support ledger solana offchain message signing ([#2093](#2093)) ([4c94443](4c94443)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
cemalkilic
pushed a commit
that referenced
this pull request
Aug 7, 2025
Some time ago a `resource_id` was added to the `sso_providers` table to support infrastructure as code use cases down the road. This change adds basic support for utilizing this field to manage SSO providers. Key changes: - Updated API for SSO providers to allow get, put, delete by `resource_id` - Extended `loadSSOProvider` to accept `resource_`-prefixed `idp_id` values - Added optional `resource_id` field to `SSOProvider` model - Implemented `FindSSOProviderByResourceID` in model layer - Renamed `FindAllSAMLProviders` to `FindAllSSOProviders` - Added filtering to the `/admin/sso/providers` via `?resource_id{,_prefix}=` - Included full E2E test coverage for SSO provider api --------- Co-authored-by: Chris Stockton <chris.stockton@supabase.io>
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.
Some time ago a
resource_id
was added to thesso_providers
table to support infrastructure as code use cases down the road. This change adds basic support for utilizing this field to manage SSO providers.Key changes:
resource_id
loadSSOProvider
to acceptresource_
-prefixedidp_id
valuesresource_id
field toSSOProvider
modelFindSSOProviderByResourceID
in model layerFindAllSAMLProviders
toFindAllSSOProviders
/admin/sso/providers
via?resource_id{,_prefix}=