Skip to main content

Using SAML for enterprise IAM

You can centrally manage accounts and access to Ihre GitHub Enterprise Server-Instance with SAML single sign-on (SSO).

Configuring SAML single sign-on for your enterprise

You can control and secure access to Ihre GitHub Enterprise Server-Instance 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 Ihre GitHub Enterprise Server-Instance, 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 Ihre GitHub Enterprise Server-Instance.

Enabling encrypted assertions

You can improve Ihre GitHub Enterprise Server-Instance'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 Ihre GitHub Enterprise Server-Instance, you must update the NameID mapping on Ihre GitHub Enterprise Server-Instance.

Troubleshooting SAML authentication

If you use SAML single sign-on (SSO) and people are unable to authenticate to access Ihre GitHub Enterprise Server-Instance, you can troubleshoot the problem.