Skip to content

Commit 2fb62b2

Browse files
authored
Add 💅
1 parent 02ff9a6 commit 2fb62b2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ If you suspect or notice that any users are not provisioned or deprovisioned as
2929

3030
To check whether users have a SCIM identity (SCIM metadata) in their external identity, you can review SCIM metadata for one organization member at a time on {% data variables.product.prodname_dotcom %} or you can programatically check all organization members using the {% data variables.product.prodname_dotcom %} API.
3131

32-
Keep in mind, when the IDP sends a provisioning call to the GitHub SCIM API, in order for the SCIM identity to get properly linked to an organization member that has an existing SAML identity, the SCIM `userName` in that API call needs to match the stored SAML `nameID` in the user's linked SAML identity in the organization. If these two attributes/values do not match, the SCIM metadata will not get populated and the SCIM identity will not get successfully linked. To check whether these values match, use the {% data variables.product.prodname_dotcom %} API.
32+
When the IdP sends a provisioning call to the {% data variables.product.prodname_dotcom %} SCIM API, the SCIM `userName` in that API call needs to match the stored SAML `nameID` in the user's linked SAML identity in the organization. If these two values do not match, the SCIM metadata will not get populated, and the SCIM identity will not get successfully linked. To check whether these values match, use the {% data variables.product.prodname_dotcom %} API.
3333

3434
#### Auditing organization members on {% data variables.product.prodname_dotcom %}
3535

0 commit comments

Comments
 (0)