Skip to main content
我们经常发布文档更新，此页面的翻译可能仍在进行中。有关最新信息，请访问英语文档。
� 

� 

此版本的 GitHub Enterprise 已停止服务 2022-10-12. 即使针对重大安全问题，也不会发布补丁。 为了获得更好的性能、更高的安全性和新功能，请升级到最新版本的 GitHub Enterprise。 如需升级帮助，请联系 GitHub Enterprise 支持。

Using SAML for enterprise IAM

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

  • About SAML for enterprise IAM

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

  • SAML configuration reference

    You can see SAML metadata for your GitHub Enterprise Server instance, and you can learn more about available SAML attributes and response requirements.

  • 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).

  • 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 your GitHub Enterprise Server instance, you must update the NameID mapping on your GitHub Enterprise Server instance.

  • Troubleshooting SAML authentication

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