Sruthi Chandran 928aa75ce0 New upstream version 12.8.6

2020-03-13 15:44:24 +05:30

11 KiB

Raw Blame History

type
howto, reference

SCIM provisioning using SAML SSO for GitLab.com groups (SILVER ONLY)

Introduced in GitLab.com Silver 11.10.

System for Cross-domain Identity Management (SCIM), is an open standard that enables the automation of user provisioning. When SCIM is provisioned for a GitLab group, membership of that group is synchronized between GitLab and the identity provider.

GitLab's SCIM API implements part of the RFC7644 protocol.

Currently, the following actions are available:

CREATE
UPDATE
DELETE (deprovisioning)

The following identity providers are supported:

Azure

Requirements

Group SSO must be configured.

GitLab configuration

Once Single sign-on has been configured, we can:

Navigate to the group and click Settings > SAML SSO.
Click on the Generate a SCIM token button.
Save the token and URL so they can be used in the next step.

Identity Provider configuration

Azure

The SAML application that was created during Single sign-on setup now needs to be set up for SCIM.

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.
Set up automatic provisioning and administrative credentials by following the Provisioning users and groups to applications that support SCIM section in Azure's SCIM setup documentation.

During this configuration, note the following:

The Tenant URL and secret token are the ones retrieved in the previous step.
Should there be any problems with the availability of GitLab or similar errors, the notification email set will get those.
It is recommended to set a notification email and check the Send an email notification when a failure occurs checkbox.
For mappings, we will only leave Synchronize Azure Active Directory Users to AppName enabled.

You can then test the connection by clicking on Test Connection. If the connection is successful, be sure to save your configuration before moving on. See below for troubleshooting.

Configure attribute mapping

Click on Synchronize Azure Active Directory Users to AppName, to configure the attribute mapping.
Click Delete next to the mail mapping.
Map userPrincipalName to emails[type eq "work"].value and change its Matching precedence to 2.
Map mailNickname to userName.
Determine how GitLab will uniquely identify users.
- Use objectId unless users already have SAML linked for your group.
- If you already have users with SAML linked then use the Name ID value from the SAML configuration. Using a different value will likely cause duplicate users and prevent users from accessing the GitLab group.
Create a new mapping:
1. Click Add New Mapping.
2. Set:
  - Source attribute to the unique identifier determined above.
  - Target attribute to id.
  - Match objects using this attribute to Yes.
  - Matching precedence to 1.
Create another new mapping:
1. Click Add New Mapping.
2. Set:
  - Source attribute to the unique identifier determined above.
  - Target attribute to externalId.
Click the userPrincipalName mapping and change Match objects using this attribute to No.

Save your changes and you should have the following configuration:

NOTE: Note: If you used a unique identifier other than objectId, be sure to map it instead to both id and externalId.
Below the mapping list click on Show advanced options > Edit attribute list for AppName.
Leave the id as the primary and only required field.

NOTE: Note: username should neither be primary nor required as we don't support that field on GitLab SCIM yet.
Save all the screens and, in the Provisioning step, set the Provisioning Status to On.

NOTE: Note: You can control what is actually synced by selecting the Scope. For example, Sync only assigned users and groups will only sync the users assigned to the application (Users and groups), otherwise, it will sync the whole Active Directory.

Once enabled, the synchronization details and any errors will appear on the bottom of the Provisioning screen, together with a link to the audit logs.

CAUTION: Warning: Once synchronized, changing the field mapped to id and externalId will likely cause provisioning errors, duplicate users, and prevent existing users from accessing the GitLab group.

User access and linking setup

As long as Group SAML has been configured, prior to turning on sync, existing GitLab.com users can link to their accounts in one of the following ways, before synchronization is active:

By updating their primary email address in their GitLab.com user account to match their identity provider's user profile email address.
By following these steps:
1. Sign in to GitLab.com if needed.
2. Click on the GitLab app in the identity provider's dashboard or visit the GitLab single sign on URL.
3. Click on the Authorize button.

New users and existing users on subsequent visits can access the group through the identify provider's dashboard or by visiting links directly.

For role information, please see the Group SAML page

Blocking access

To rescind access to the group, we recommend removing the user from the identity provider or users list for the specific app.

Upon the next sync, the user will be deprovisioned, which means that the user will be removed from the group. The user account will not be deleted unless using group managed accounts.

Troubleshooting

This section contains possible solutions for problems you might encounter.

How do I verify my SCIM configuration is correct?

Review the following:

Ensure that the SCIM value for id matches the SAML value for NameId.
Ensure that the SCIM value for externalId matches the SAML value for NameId.

Review the following SCIM parameters for sensible values:

userName
displayName
emails[type eq "work"].value

Testing Azure connection: invalid credentials

When testing the connection, you may encounter an error: You appear to have entered invalid credentials. Please confirm you are using the correct information for an administrative account. If Tenant URL and secret token are correct, check whether your group path contains characters that may be considered invalid JSON primitives (such as .). Removing such characters from the group path typically resolves the error.

Azure: (Field) can't be blank sync error

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.

As a workaround, try an alternate mapping:

Follow the Azure mapping instructions from above.
Delete the name.formatted target attribute entry.
Change the displayName source attribute to have name.formatted target attribute.

The Identity (extern_uid) value stored by GitLab is updated by SCIM whenever id or externalId changes. Users won't be able to sign in unless the GitLab Identity (extern_uid) value matches the NameId sent by SAML.

This value is also used by SCIM to match users on the id, and is updated by SCIM whenever the id or externalId values change.

It is important that this SCIM id and SCIM externalId are configured to the same value as the SAML NameId. SAML responses can be traced using debugging tools, and any errors can be checked against our SAML troubleshooting docs.

How do I verify user's SAML NameId matches the SCIM externalId

Group owners can see the list of users and the externalId stored for each user in the group SAML SSO Settings page.

Alternatively, the SCIM API can be used to manually retrieve the externalId we have stored for users, also called the external_uid or NameId.

For example:

curl 'https://example.gitlab.com/api/scim/v2/groups/GROUP_NAME/Users?startIndex=1"' --header "Authorization: Bearer <your_scim_token>" --header "Content-Type: application/scim+json"

To see how this compares to the value returned as the SAML NameId, you can have the user use a SAML Tracer.

Fix mismatched SCIM externalId and SAML NameId

If GitLab's externalId doesn't match the SAML NameId, it will need to be updated in order for the user to log in. Ideally your identity provider will be configured to do such an update, but in some cases it may be unable to do so, such as when looking up a user fails due to an ID change.

Fixing the fields your SCIM identity provider sends as id and externalId can correct this, however we use these IDs to look up users so if the identity provider is unaware of the current values for these it may try to create new duplicate users instead.

If the externalId we have stored for a user has an incorrect value that doesn't match the SAML NameId, then it can be corrected with the manual use of the SCIM API.

The SCIM API can be used to manually correct the externalId stored for users so that it matches the SAML NameId. You'll need to know the desired value that matches the NameId as well as the current externalId to look up the user.

It is then possible to issue a manual SCIM#update request, for example:

curl --verbose --request PATCH 'https://gitlab.com/api/scim/v2/groups/YOUR_GROUP/Users/OLD_EXTERNAL_UID' --data '{ "Operations": [{"op":"Replace","path":"externalId","value":"NEW_EXTERNAL_UID"}] }' --header "Authorization: Bearer <your_scim_token>" --header "Content-Type: application/scim+json"

It is important not to update these to incorrect values, since this will cause users to be unable to sign in. It is also important not to assign a value to the wrong user, as this would cause users to get signed into the wrong account.

11 KiB Raw Blame History