Skip to main content

Esta versión de GitHub Enterprise Server se discontinuará el 2026-03-17. No se realizarán lanzamientos de patch, ni siquiera para problemas de seguridad críticos. Para obtener rendimiento mejorado, seguridad mejorada y nuevas características, actualice a la versión más reciente de GitHub Enterprise Server. Para obtener ayuda con la actualización, póngase en contacto con el soporte técnico de GitHub Enterprise.

Identity and access management fundamentals

Administrators must decide how users will access the enterprise's resources on GitHub.

What is IAM for GitHub?

Administrators who configure a GitHub Enterprise Server instance can use local accounts and built-in authentication on the instance. Alternatively, to centralize identity and access for an enterprise's web applications, administrators can configure an external authentication method. If you use SAML, you can optionally provision user accounts on the instance from your identity provider (IdP) using System for Cross-domain Identity Management (SCIM).

Which authentication method are available to me?

The following authentication methods are available for GitHub Enterprise Server.

Built-in authentication

Cuando se usa la autenticación integrada para tu instancia de GitHub Enterprise Server, cada usuario crea una cuenta personal a partir de una invitación o al registrarse. To access your instance, people authenticate with the credentials for the account. For more information, see Configurar la autenticación integrada.

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 tu instancia de GitHub Enterprise Server. For more information, see the following articles.

Nota:

Puedes usar SAML o LDAP, pero no ambos.

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 Permitir la autenticación integrada de los usuarios ajenos al proveedor.

How does provisioning work?

If you configure built-in authentication, CAS, LDAP, or SAML, GitHub Enterprise Server creates a user account when an authorized person signs into the instance, or "just in time" (JIT). Optionally, if you use SAML, you can provision user accounts from your identity provider (IdP) using SCIM. For more information, see Acerca del aprovisionamiento de usuarios con SCIM en GitHub Enterprise Server.

Further reading