What is IAM for GitHub?
Administrators who configure a GitHub Enterprise Server instance can use local accounts and built-in authentication on the instance. Alternatively, to centralize identity and access for an enterprise's web applications, administrators can configure an external authentication method. If you use SAML, you can optionally provision user accounts on the instance from your identity provider (IdP) using System for Cross-domain Identity Management (SCIM).
Which authentication method are available to me?
The following authentication methods are available for GitHub Enterprise Server.
Built-in authentication
When you use built-in authentication for your GitHub Enterprise Server instance, each person creates a personal account from an invitation or by signing up. To access your instance, people authenticate with the credentials for the account. For more information, see Configuring built-in authentication.
External authentication
If you use an external directory or identity provider (IdP) to centralize access to multiple web applications, you may be able to configure external authentication for your GitHub Enterprise Server instance. For more information, see the following articles.
Hinweis
You can use either SAML or LDAP, but not both.
If you choose to use external authentication, you can also configure fallback authentication for people who don't have an account on your external authentication provider. For example, you may want to grant access to a contractor or machine user. For more information, see Allowing built-in authentication for users outside your provider.
How does provisioning work?
If you configure built-in authentication, CAS, LDAP, or SAML, GitHub Enterprise Server creates a user account when an authorized person signs into the instance, or "just in time" (JIT). Optionally, if you use SAML, you can provision user accounts from your identity provider (IdP) using SCIM. For more information, see About user provisioning with SCIM on GitHub Enterprise Server.