diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-02-24 03:09:02 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-02-24 03:09:02 +0300 |
commit | 2ed3b0abccc8de391f1a9de2bc5785d3e0f5b018 (patch) | |
tree | fd6a1c298cb159656c72d622d5844fb55e191913 /doc/user/group | |
parent | 9083509f2f0e424b1d53cca4877d994d2050562b (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/group')
-rw-r--r-- | doc/user/group/saml_sso/index.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/user/group/saml_sso/index.md b/doc/user/group/saml_sso/index.md index 73ac54905e3..b09dba573f2 100644 --- a/doc/user/group/saml_sso/index.md +++ b/doc/user/group/saml_sso/index.md @@ -295,6 +295,8 @@ For convenience, we've included some [example resources](../../../administration In troubleshooting the Group SAML setup, any authenticated user can use the API to verify the NameID GitLab already has linked to the user by visiting [https://gitlab.com/api/v4/user](https://gitlab.com/api/v4/user) and checking the `extern_uid` under identities. +Similarly, group members of a role with the appropriate permissions can make use of the [members API](../../../api/members.md) to view group SAML identity information for members of the group. + This can then be compared to the [NameID](#nameid) being sent by the Identity Provider by decoding the message with a [SAML debugging tool](#saml-debugging-tools). We require that these match in order to identify users. ### Message: "SAML authentication failed: Extern uid has already been taken" |