Enterprise administrators guides

使用しているプロバイダーの外部ユーザーのためのビルトイン認証の許可

CAS、LDAP、または SAML 認証プロバイダーにアカウントを持っていないユーザーに対して組み込みの認証を許可するように、フォールバック認証を構成できます。

• Accounts
• Authentication
• Enterprise
• Identity

Changing authentication methods

You can change the way GitHub Enterprise Server authenticates with your existing accounts at any time.

• Accounts
• Authentication
• Enterprise
• Identity

Configuring SAML single sign-on for your enterprise

You can control and secure access to your GitHub Enterprise Server instance by configuring SAML single sign-on (SSO) through your identity provider (IdP).

• Accounts
• Authentication
• Enterprise
• Identity
• SSO

About SAML for enterprise IAM

You can use SAML single sign-on (SSO) to centrally manage access to your GitHub Enterprise Server instance.

• Accounts
• Access management
• Authentication
• Enterprise
• Identity

Configuring SAML single sign-on for your enterprise

You can control and secure access to your GitHub Enterprise Server instance by configuring SAML single sign-on (SSO) through your identity provider (IdP).

• Accounts
• Authentication
• Enterprise
• Identity
• SSO

Using CAS

If you use Central Authentication Service (CAS) to centralize access to multiple web applications, you can integrate GitHub Enterprise Server by configuring CAS authentication for your instance.

• Accounts
• Authentication
• Enterprise
• Identity
• SSO

Using LDAP

If you use Lightweight Directory Access Protocol (LDAP) to centralize access across applications, you can integrate GitHub Enterprise Server by configuring LDAP authentication for your instance.

• Accounts
• Authentication
• Enterprise
• Identity

Using SAML for enterprise IAM

You can centrally manage accounts and access to your GitHub Enterprise Server instance with SAML single sign-on (SSO).

Accessing the administrative shell (SSH)

SSHアクセスによって、トラブルシューティング、バックアップの実行、レプリケーションの設定のためにGitHub Enterprise Serverのコマンドラインユーティリティを実行できます。

• Enterprise
• Fundamentals
• SSH