Support workspace with SSO enforced #4227
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
fontanierh
approved these changes
Mar 8, 2024
flvndvd
added
the
migration-ack
This was referenced Mar 8, 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.
Description
This PR introduces a new feature that allows workspace administrators to enforce Single Sign-On (SSO) for all users within their workspace. By enabling the SSO enforcement option, admins can ensure that every user logs in exclusively through the designated SSO provider.
This check needs to happen at the server side rendering time to ensure that the check applies anytime an admin update the settings.
This does not expose this setting yet in the UI. We first need to be able to merge accounts before doing so.
Risk
Deploy Plan
This requires to run a migration to add the
ssoEnforcedfield on theWorkspacemodel.