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
当你对 你的 GitHub Enterprise Server 实例 使用内置身份验证时，每个人都会从邀请中或通过注册来创建个人帐户。 To access your instance, people authenticate with the credentials for the account. For more information, see 配置内置身份验证.
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 你的 GitHub Enterprise Server 实例. For more information, see the following articles.
注意
可以使用 SAML 或 LDAP，但不能同时使用两者。
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 允许对提供程序覆盖范围之外的用户进行内置身份验证.
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 关于 GitHub Enterprise Server 上的 SCIM 用户预配.