Feat: Remove Composite Identity Enforced Setting

What does this MR do and why?

This MR addresses moving the Composite Identity Enforced setting from Duo Settings on the Instance/Admin level.

References

Related GitLab Issue: #588629 (closed)

Screenshots or screen recordings

Before After
SaaS Screenshot_2026-02-11_at_12.25.57_AM Screenshot_2026-02-11_at_12.22.18_AM
Self-Managed Screenshot_2026-02-11_at_12.24.29_AM Screenshot_2026-02-11_at_12.23.39_AM

How to set up and validate locally

Testing Notes

    1. Be sure to test this in both SaaS and SM by using the following commands with gdk start: SaaS (GITLAB_SIMULATE_SAAS=1) & SM (GITLAB_SIMULATE_SAAS=0)

Test Removed Setting

    1. Go to the GitLab Duo settings at the instance level: Admin > GitLab Duo (in left navigation). Note, if you are in SaaS mode - the page should no longer display in the navigation - and if you go to the page via the path it should now return 404.
    1. Validate the Composite Identity setting is no longer displayed in Self-Managed.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #588629 (closed)

Edited by Lindsey Shelton

Merge request reports

Loading