Skip to content

Commit bd2fb98

Browse files
authored
Merge pull request #33933 from github/repo-sync
repo sync
2 parents 408f6b0 + 34e0933 commit bd2fb98

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,8 @@ 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+
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.
33+
3234
#### Auditing organization members on {% data variables.product.prodname_dotcom %}
3335

3436
As an organization owner, to confirm that SCIM metadata exists for a single organization member, visit this URL, replacing `<organization>` and `<username>`:

0 commit comments

Comments
 (0)