我们经常发布文档更新,此页面的翻译可能仍在进行中。有关最新信息,请访问英文文档。如果此页面上的翻译有问题,请告诉我们

此版本的 GitHub Enterprise 将停止服务 此版本的 GitHub Enterprise 已停止服务 2020-08-20. 即使针对重大安全问题,也不会发布补丁。 要获得更好的性能、改进的安全性和新功能,请升级到 GitHub Enterprise 的最新版本。 如需升级方面的帮助,请联系 GitHub Enterprise 支持

文章版本: Enterprise Server 2.18

Changing authentication methods

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

User accounts on 您的 GitHub Enterprise Server 实例 are preserved when you change the authentication method and users will continue to log into the same account as long as their username doesn't change.

If the new method of authentication changes usernames, new accounts will be created. As an administrator, you can rename users through the site admin settings or by using the User Administration API.

Other issues you should take into consideration include:

  • Passwords: If you switch to using built-in authentication for your instance, users must set a password after the change is completed.

  • Site administrators: Administrative privileges are controlled by your identity provider when you use SAML and can be controlled by group membership when you use LDAP.

  • Team membership: Only LDAP lets you control team membership from your directory server.

  • User suspension: When you use LDAP to authenticate, access to GitHub Enterprise Server can be controlled via restricted groups. After switching to LDAP, if restricted groups are configured, existing users who are not in one of those groups will be suspended. Suspension will occur either when they log in or during the next LDAP Sync.

  • Group membership: When you use LDAP to authenticate, users are automatically suspended and unsuspended based on restricted group membership and account status with Active Directory.

  • Git authentication: SAML and CAS only supports Git authentication over HTTP or HTTPS using a personal access token. Password authentication over HTTP or HTTPS is not supported. LDAP supports password-based Git authentication by default, but we recommend that you disable that method and force authentication via a personal access token or SSH key.

  • API authentication: SAML and CAS only supports API authentication using a personal access token. Basic authentication is not supported.

  • Two-factor authentication: 使用 SAML 或 CAS 时,双重身份验证在 GitHub Enterprise Server 设备上不受支持或无法管理,但受外部身份验证提供商的支持。 在组织上无法实施双重身份验证。 有关在组织上实施双重身份验证的更多信息,请参阅“您的组织中需要双重身份验证”。

  • Built-in authentication for users outside your identity provider: You can invite users to authenticate to 您的 GitHub Enterprise Server 实例 without adding them to your identity provider. For more information, see "Allowing built-in authentication for users outside your identity provider."

问问别人

找不到要找的内容?

联系我们