Follow-up from "Allow GitLab.com to use the assertion "nickname" and "username" when integrating with SAML"
The following discussion from !72134 (merged) should be addressed:
-
@cynthia started a discussion: (+3 comments) ### `attribute_statements`
TW can confirm, but I believe if it's "inherited" from the level 2 heading, we don't badge.
Summary
From the "SAML SSO for GitLab.com Groups" documentation we link from the Assertions section to the Self-managed SAML Assertions List documentation. This was done to avoid duplication of content. This section then leads deeper into Self-managed docs by linking to attribute_statements section.
The concern is once the user is linked to this page they might be misled and think that the attribute_statements
section (and the rest of this page) is relevant to SSO for GitLab.com. @dblessing attempted to make this clearer by adding a tier badge to this sub-section. However, this goes against our docs guidelines by tiering a sub-section which might also cause confusion.
How do we handle this? Is it best to duplicate content? To break it out into another page? Other?