diff options
| author | Cynthia Ng <cng@gitlab.com> | 2019-07-30 15:21:47 +0000 |
|---|---|---|
| committer | cynthiang <cng@gitlab.com> | 2019-07-30 10:25:54 -0700 |
| commit | 4c548c635360564282fe65483d76c6e7e4748e6c (patch) | |
| tree | 31ef7d7d31756ef2c626848867754f14bb844aee | |
| parent | a06299e9398024eafdefd70c426797abbf96d9b1 (diff) | |
| download | gitlab-ce-docs-ee-13016.tar.gz | |
Apply suggestion to doc/user/group/saml_sso/scim_setup.mddocs-ee-13016
| -rw-r--r-- | doc/user/group/saml_sso/scim_setup.md | 10 |
1 files changed, 3 insertions, 7 deletions
diff --git a/doc/user/group/saml_sso/scim_setup.md b/doc/user/group/saml_sso/scim_setup.md index e18a300478b..64ac4f15d5f 100644 --- a/doc/user/group/saml_sso/scim_setup.md +++ b/doc/user/group/saml_sso/scim_setup.md @@ -126,14 +126,10 @@ When testing the connection, you may encounter an error: **You appear to have en ### Azure: (Field) can't be blank sync error -When checking the Audit Logs for the Provisioning, you can sometimes see "can't be -blank" errors such as: +When checking the Audit Logs for the Provisioning, you can sometimes see the +error `Namespace can't be blank, Name can't be blank, and User can't be blank.` -- `Namespace can't be blank`. -- `Name can't be blank`. -- `User can't be blank`. - -These are likely caused because not all required fields (such as first name and +This is likely caused because not all required fields (such as first name and last name) are present for all users being mapped. As a workaround, try an alternate mapping: |