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을 사용하여 사용자 프로비전 정보.