diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-08-23 21:10:41 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-08-23 21:10:41 +0300 |
| commit | 6a6e9bec88480863cc3e8fb5edc50744e00da964 (patch) | |
| tree | e663d6c9fe29259dd53f7bf10d4f5f796d467a2e /doc/user/group/saml_sso/troubleshooting_scim.md | |
| parent | 9919ffe0c8760e1e19e068d67a5ae6ae8aa67c5d (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/group/saml_sso/troubleshooting_scim.md')
| -rw-r--r-- | doc/user/group/saml_sso/troubleshooting_scim.md | 13 |
1 files changed, 12 insertions, 1 deletions
diff --git a/doc/user/group/saml_sso/troubleshooting_scim.md b/doc/user/group/saml_sso/troubleshooting_scim.md index 7d2aa8faa99..4a66719b020 100644 --- a/doc/user/group/saml_sso/troubleshooting_scim.md +++ b/doc/user/group/saml_sso/troubleshooting_scim.md @@ -13,7 +13,18 @@ This section contains possible solutions for problems you might encounter. When you remove a user, they are removed from the group but their account is not deleted (see [remove access](scim_setup.md#remove-access)). -When the user is added back to the SCIM app, GitLab cannot create a new user because the user already exists. +When the user is added back to the SCIM app, GitLab does not create a new user because the user already exists. + +From August 11, 2023, the `skip_saml_identity_destroy_during_scim_deprovision` feature flag is enabled. + +For a user de-provisioned by SCIM from that date, their SAML identity is not removed. + +When that user is added back to the SCIM app: + +- Their SCIM identity `active` attribute is set to `true`. +- They can sign in using SSO. + +For users de-provisioned by SCIM before that date, their SAML identity is destroyed. To solve this problem: |