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 を使ったユーザー プロビジョニングについて.