Using SAML for enterprise IAM
You can centrally manage accounts and access to GitHub Enterprise Server 인스턴스 with SAML single sign-on (SSO).
Configuring SAML single sign-on for your enterprise
You can control and secure access to GitHub Enterprise Server 인스턴스 by configuring SAML single sign-on (SSO) through your identity provider (IdP).
Configuring user provisioning with SCIM for your enterprise
You can configure System for Cross-domain Identity Management (SCIM) for GitHub Enterprise Server 인스턴스, which automatically provisions user accounts when you assign the application for your instance to a user on your identity provider (IdP).
Configuring authentication and provisioning for your enterprise using Entra ID
You can use a tenant in Microsoft Entra ID (previously known as Azure AD) as an identity provider (IdP) to centrally manage authentication and user provisioning for GitHub Enterprise Server 인스턴스.
Enabling encrypted assertions
You can improve GitHub Enterprise Server 인스턴스's security with SAML single sign-on (SSO) by encrypting the messages that your SAML identity provider (IdP) sends.
Updating a user's SAML NameID
When an account's NameID changes on your identity provider (IdP) and the person can no longer sign into GitHub Enterprise Server 인스턴스, you must update the NameID mapping on GitHub Enterprise Server 인스턴스.
Troubleshooting SAML authentication
If you use SAML single sign-on (SSO) and people are unable to authenticate to access GitHub Enterprise Server 인스턴스, you can troubleshoot the problem.