Skip to content

Add transparent sso override feature flag

Drew Blessing requested to merge dblessing_transparent_sso_add_disable_ff into master

What does this MR do and why?

Describe in detail what your merge request does and why.

Related to the rollout of Transparent SSO Enforcement. Due to edge cases and potential customer impact, this change introduces an override feature flag to allow selective disablement of the new feature. This will allow support to rollback the change for individual customers if they are too negatively impacted, while we work to address that particular customer's concerns, without requiring us to rollback the entire feature flag for all customers. The path forward was discussed in the rollout issue at #375788 (comment 1198802139).

Both flags are scoped to top level groups:

  • Main feature flag - transparent_sso_enforcement.
  • Override feature flag - transparent_sso_enforcement_override

Cases:

  • transparent_sso_enforcement is enabled, transparent_sso_enforcement_override is disabled
    • Transparent SSO is enabled
  • transparent_sso_enforcement is enabled, transparent_sso_enforcement_override is enabled.
    • Transparent SSO is disabled

This MR also contains documentation updates to better reflect the current state of transparent SSO rollout as well as both self-serve troubleshooting documentation and tips for GitLab team members (Support or Production) to override the feature per group.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Drew Blessing

Merge request reports