Skip to main content
We publish frequent updates to our documentation, and translation of this page may still be in progress. For the most current information, please visit the English documentation.
 

 

Using SAML for enterprise IAM

You can centrally manage accounts and access to GitHub Enterprise Serverインスタンス with SAML single sign-on (SSO).

  • About SAML for enterprise IAM

    You can use SAML single sign-on (SSO) to centrally manage access to GitHub Enterprise Serverインスタンス.

  • SAML configuration reference

    You can see SAML metadata for GitHub Enterprise Serverインスタンス, and you can learn more about available SAML attributes and response requirements.

  • Enterprise 向けの SAML シングルサインオンを設定する

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

  • Enabling encrypted assertions

    You can improve GitHub Enterprise Serverインスタンス's security with SAML single sign-on (SSO) by encrypting the messages that your SAML identity provider (IdP) sends.

  • Updating a user's SAML NameID

    When an account's NameID changes on your identity provider (IdP) and the person can no longer sign into GitHub Enterprise Serverインスタンス, you must update the NameID mapping on GitHub Enterprise Serverインスタンス.

  • SAML認証

    If you use SAML single sign-on (SSO) and people are unable to authenticate to access GitHub Enterprise Serverインスタンス, you can troubleshoot the problem.