[Gitlab Docuemntation: Require user re-authentication to approve ](https://docs.gitlab.com/user/project/merge_requests/approvals/settings/#require-user-re-authentication-to-approve) ### Release notes For those leveraging SAML SSO/SCIM for user account management in GitLab, users may instead leverage their SSO to meet the merge request authentication requirement over password based authentication for approving merge requests. This method ensures only authenticated users can approve a merge request for security and compliance, without having to use a separate password-based solution. ### Problem to Solve GitLab currently supports [requiring user passwords to approve](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/settings.html#require-user-password-to-approve) merge requests. However, this feature also requires the use of password authentication for the GitLab web interface. In many cases organizations are choosing SAML SSO/SCIM based solutions for their user account management on GitLab and so users don't have nor would organizations like for those users to have passwords to GitLab. ### Proposal When the setting for `require user password to approve` is enabled, if the option for [password authentication](https://docs.gitlab.com/ee/user/admin_area/settings/sign_in_restrictions.html#password-authentication-enabled) is disabled, the button should prompt the user to re-authenticate with their currently configured and enabled sign-in provider(s). ### Available Tier <!-- This section should be used for setting the appropriate tier that this feature will belong to. Pricing can be found here: https://about.gitlab.com/pricing/ * Free * Premium/Silver * Ultimate/Gold --> ~"GitLab Premium" SAML is a Premium+ feature. SAML is typically configured at the group level, so whether that correlates with team or not depends on how the customer sets up their structure. By adding this feature at the Premium tier, it will align with our other SAML features. ### Additional Details There's a POC of some of this in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/79876 - but it's also extending to support MFA authentication. _This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc._ <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->