Troubleshooting SCIM

Tier: Free, Premium, Ultimate Offering: GitLab.com, Self-managed, GitLab Dedicated

This section contains possible solutions for problems you might encounter.

User cannot be added after they are removed

When you remove a user, they are removed from the group but their account is not deleted (see remove access).

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, the user must link SAML to their existing GitLab.com account.

Self-managed GitLab

For a self-managed GitLab instance, administrators of that instance can instead add the user identity themselves. This might save time if administrators need to re-add multiple identities.

User cannot sign in

The following are possible solutions for problems where users cannot sign in:

  • Ensure that the user was added to the SCIM app.
  • If you receive the User is not linked to a SAML account error, the user probably already exists in GitLab. Have the user follow the Link SCIM and SAML identities instructions. Alternatively, self-managed administrators can add a user identity.
  • The Identity (extern_uid) value stored by GitLab is updated by SCIM whenever id or externalId changes. Users cannot sign in unless the GitLab identifier (extern_uid) of the sign-in method matches the ID sent by the provider, such as 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.
  • On GitLab.com, the SCIM id and SCIM externalId must be configured to the same value as the SAML NameId. You can trace SAML responses using debugging tools, and check any errors against the SAML troubleshooting information.

Unsure if user’s SAML NameId matches the SCIM externalId

To check if a user’s SAML NameId matches their SCIM externalId:

  • Administrators can use the Admin Area to list SCIM identities for a user.
  • Group owners can see the list of users and the identifier stored for each user in the group SAML SSO Settings page.
  • You can use the SCIM API to manually retrieve the extern_uid GitLab has stored for users and compare the value for each user from the SAML API .
  • Have the user use a SAML Tracer and compare the extern_uid to the value returned as the SAML NameId.

Mismatched SCIM extern_uid and SAML NameId

Whether the value was changed or you need to map to a different field, the following must map to the same field:

  • externalId
  • NameId

If the GitLab extern_uid does not match the SAML NameId, you must update the GitLab extern_uid to enable the user to sign in.

Be cautious if you revise the fields used by your SCIM identity provider, typically externalId. Your identity provider should be configured to do this update. In some cases the identity provider cannot do the update, for example when a user lookup fails.

GitLab uses these IDs to look up users. If the identity provider does not know the current values for these fields, that provider may create duplicate users, or fail to complete expected actions.

To change the identifier values to match, you can do one of the following:

You must not:

  • Update these to incorrect values because this causes users to be unable to sign in.
  • Assign a value to the wrong user because this causes users to be signed in to the wrong account.

Additionally, the user’s primary email must match the email in your SCIM identity provider.

Change SCIM app

When the SCIM app changes:

  • Users can follow the instructions in the Change the SAML app section.
  • Administrators of the identity provider can:
    1. Remove users from the SCIM app, which:
      • In GitLab.com, removes all removed users from the group.
      • In GitLab self-managed, blocks users.
    2. Turn on sync for the new SCIM app to link existing users.

SCIM app returns "User has already been taken","status":409 error

Tier: Premium, Ultimate Offering: GitLab.com

Changing the SAML or SCIM configuration or provider can cause the following problems:

The member’s email address is not allowed for this group

SCIM provisioning may fail with HTTP status 412 and the following error message: 

The member's email address is not allowed for this group. Check with your administrator.

This error occurs when both of the following are true:

To resolve this issue, you can do either of the following:

Search Rails logs for SCIM requests

Tier: Premium, Ultimate Offering: GitLab.com

GitLab.com administrators can search for SCIM requests in the api_json.log using the pubsub-rails-inf-gprd-* index in Kibana. Use the following filters based on the internal group SCIM API:

  • json.path: /scim/v2/groups/<group-path>
  • json.params.value: <externalId>

In a relevant log entry, the json.params.value shows the values of SCIM parameters GitLab receives. Use these values to verify if SCIM parameters configured in an identity provider’s SCIM app are communicated to GitLab as intended.

For example, use these values as a definitive source on why an account was provisioned with a certain set of details. This information can help where an account was SCIM provisioned with details that do not match the SCIM app configuration.

Member’s email address is not linked error in SCIM log

When you attempt to provision a SCIM user on GitLab.com, GitLab checks to see if a user with that email address already exists. You might see the following error when the:

  • User exists, but does not have a SAML identity linked.
  • User exists, has a SAML identity, and has a SCIM identity that is set to active: false. 
The member's email address is not linked to a SAML account or has an inactive
SCIM identity.

This error message is returned with the status 412.

This might prevent the affected end user from accessing their account correctly.

The first workaround is:

  1. Have the end user link SAML to their existing GitLab.com account.
  2. After the user has done this, initiate a SCIM sync from your identity provider. If the SCIM sync completes without the same error, GitLab has successfully linked the SCIM identity to the existing user account, and the user should now be able to sign in using SAML SSO.

If the error persists, the user most likely already exists, has both a SAML and SCIM identity, and a SCIM identity that is set to active: false. To resolve this:

  1. Optional. If you did not save your SCIM token when you first configured SCIM, generate a new token. If you generate a new SCIM token, you must update the token in your identity provider’s SCIM configuration, or SCIM will stop working.
  2. Locate your SCIM token.
  3. Use the API to get a single SCIM provisioned user.

  4. Check the returned information to make sure that:

    • The user’s identifier (id) and email match what your identity provider is sending.
    • active is set to false.

    If any of this information does not match, contact GitLab Support.

  5. Use the API to update the SCIM provisioned user’s active value to true.
  6. If the update returns a status code 204, have the user attempt to sign in using SAML SSO.

Azure Active Directory

The following troubleshooting information is specifically for SCIM provisioned through Azure Active Directory.

Verify my SCIM configuration is correct

Ensure that:

  • The matching precedence for externalId is 1.
  • 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

invalid credentials error when testing connection

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 or URL encoding these characters in the group path typically resolves the error.

(Field) can't be blank sync error

When checking the Audit Events for the provisioning, you sometimes see a Namespace can't be blank, Name can't be blank, and User can't be blank. error.

This error can occur 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:

  1. Follow the Azure mapping instructions.
  2. Delete the name.formatted target attribute entry.
  3. Change the displayName source attribute to have name.formatted target attribute.

Failed to match an entry in the source and target systems Group 'Group-Name' error

Group provisioning in Azure can fail with the Failed to match an entry in the source and target systems Group 'Group-Name' error. The error response can include a HTML result of the GitLab URL https://gitlab.com/users/sign_in.

This error is harmless and occurs because group provisioning was turned on but GitLab SCIM integration does not support it nor require it. To remove the error, follow the instructions in the Azure configuration guide to disable the option to synchronize Azure Active Directory groups to AppName.

Okta

The following troubleshooting information is specifically for SCIM provisioned through Okta.

Error authenticating: null message when testing API SCIM credentials

When testing the API credentials in your Okta SCIM application, you may encounter an error: 

Error authenticating: null

Okta needs to be able to connect to your GitLab instance to provision or deprovision users.

In your Okta SCIM application, check that the SCIM Base URL is correct and pointing to a valid GitLab SCIM API endpoint URL. Check the following documentation to find information on this URL for:

For self-managed GitLab instances, ensure that GitLab is publicly available so Okta can connect to it. If needed, you can allow access to Okta IP addresses on your firewall.