jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 21:07:12 -05:00
Code Issues Projects Releases Wiki Activity

Damienbutler GHES SCIM table network requirements for configuring SCIM provisioning (#57991)

Browse Source 
Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This commit is contained in:
Damien Butler
2025-10-31 07:58:40 +00:00
committed by GitHub
parent 1d8f219861
commit d4691afedf
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
content/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-scim-provisioning-for-users.md
View File

@@ -58,6 +58,14 @@ If you're configuring SCIM provisioning for a new enterprise, make sure to compl
{% else %}
* SCIM is a server-to-server protocol. Your instance's REST API endpoints must be accessible to your SCIM provider.
This table contains the network requirements to configure GHES SCIM with an IdP:
| System | Direction | Purpose | Protocol / Port | Notes |
|------------|------------|----------|------------------|-------|
| GitHub Enterprise Server | Inbound | Receives SCIM API requests from IdP for users and groups | TCP 443 (HTTPS) | [AUTOTITLE](/enterprise-server/rest/enterprise-admin/scim) must be reachable from IdP |
| Identity Provider (IdP) | Outbound | Sends SCIM provisioning requests to GitHub for users and groups | TCP 443 (HTTPS) | IdP acts as SCIM client, initiating outbound HTTPS connections to GitHub's SCIM API endpoints. |
* For authentication, your instance must use SAML SSO, or a mix of SAML and built-in authentication.
* You cannot mix SCIM with other external authentication methods. If you use CAS or LDAP, you will need to migrate to SAML before using SCIM.
* After you have configured SCIM, you must keep SAML authentication enabled to continue using SCIM.