diff options
| author | Tristan Williams <twilliams@gitlab.com> | 2019-08-15 19:09:35 -0700 |
|---|---|---|
| committer | Tristan Williams <twilliams@gitlab.com> | 2019-08-15 19:09:35 -0700 |
| commit | e7f7eee33a0b7e8d9df1d3dde415686888923552 (patch) | |
| tree | f0870fe5dd161d02c9ca78fcecdb87b833a27138 | |
| parent | 465c73bf1318811d4c080fc2603a93b1e580d518 (diff) | |
| download | gitlab-ce-docs-resolve-65097.tar.gz | |
Resolve docs linting errordocs-resolve-65097
| -rw-r--r-- | doc/user/group/saml_sso/scim_setup.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/user/group/saml_sso/scim_setup.md b/doc/user/group/saml_sso/scim_setup.md index 7ed7276667b..2015c81bf5c 100644 --- a/doc/user/group/saml_sso/scim_setup.md +++ b/doc/user/group/saml_sso/scim_setup.md @@ -63,7 +63,7 @@ The SAML application that was created during [Single sign-on](index.md) setup no 1. Check the configuration for your GitLab SAML app and ensure that **Name identifier value** (NameID) points to `user.objectid` or another unique identifier. This will match the `extern_uid` used on GitLab. -  + 1. Set up automatic provisioning and administrative credentials by following the [Provisioning users and groups to applications that support SCIM](https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/use-scim-to-provision-users-and-groups#provisioning-users-and-groups-to-applications-that-support-scim) section in Azure's SCIM setup documentation. @@ -96,6 +96,7 @@ You can then test the connection by clicking on **Test Connection**. If the conn NOTE: **Note:** If you used a unique identifier **other than** `objectId`, be sure to map it instead to both `id` and `externalId`. 1. Below the mapping list click on **Show advanced options > Edit attribute list for AppName**. + 1. Leave the `id` as the primary and only required field. NOTE: **Note:** @@ -128,8 +129,7 @@ When testing the connection, you may encounter an error: **You appear to have en 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.` -This is likely caused because not all required fields (such as first name and -last name) are present for all users being mapped. +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: |