The SAML SSO for GitLab.com groups is confusing as it refers to Premium
What does this MR do?
Problem:
As noted in #251138 (closed), the SAML SSO for GitLab.com groups should only be for gitlab.com which means that any product tier tags should only refer to gitlab.com tiers. The top of the page refers to both Premium and Silver. Having Premium listed on the page makes it appear like it is a self-managed feature.
Objective:
Make it possible to label https://docs.gitlab.com/ee/user/group/saml_sso/ as (SILVER ONLY)
Solution:
Move Configuring on a self-managed GitLab instance from its current location at doc/user/group/saml_sso/index.md to the SAML OmniAuth Provider page
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Closes #251138 (closed)