Skip to main content
ドキュメントには頻繁に更新が加えられ、その都度公開されています。本ページの翻訳はまだ未完成な部分があることをご了承ください。最新の情報については、英語のドキュメンテーションをご参照ください。本ページの翻訳に問題がある場合はこちらまでご連絡ください。

About authentication for your enterprise

You can choose how people authenticate to access GitHub Enterprise Serverインスタンス.

About authentication for your enterprise

Site administrators can decide how people authenticate to access a GitHub Enterprise Server instance. You can use GitHub Enterprise Server's built-in authentication, or, if you want to centralize identity and access management for the web applications that your team uses, you can configure an external authentication method.

Authentication methods for GitHub Enterprise Server

The following authentication methods are available for GitHub Enterprise Server.

Built-in authentication

When you use built-in authentication for GitHub Enterprise Serverインスタンス, 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. 詳しい情報については、「ビルトイン認証の設定」を参照してください。

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インスタンス. 詳しい情報については、以下を参照してください。

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."

参考リンク