About authentication with SSO
El inicio de sesión único (SSO) de SAML proporciona a los propietarios de la organización y de la empresa una manera de controlar y proteger el acceso a los recursos de la organización, como repositorios, incidencias y solicitudes de incorporación de cambios. Organization owners can invite your personal account on GitHub to join their organization that uses SSO, which allows you to contribute to the organization and retain your existing identity and contributions on GitHub.
Access to SSO protected internal resources in an enterprise, such as repositories, projects, and packages, requires an SSO session for any organization in the enterprise. This allows code and work to be shared across organizations in an enterprise without requiring users to join each organization.
If you're a member of an empresa con usuarios administrados, you will instead use a new account that is provisioned for you and controlled by your enterprise. Para más información, consulta Tipos de cuentas de GitHub.
When you attempt to access most resources within an organization that uses SSO, GitHub will redirect you to the organization's SSO identity provider (IdP) to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to GitHub, where you can access the organization's resources.
La autenticación de IdP no es necesaria para acceder a repositorios públicos de determinadas maneras:
- Visualización de la página de información general del repositorio y el contenido del archivo en GitHub
- Bifurcación del repositorio
- Realización de operaciones de lectura a través de Git, como clonación del repositorio
La autenticación es necesaria para otro acceso a repositorios públicos, como ver problemas, solicitudes de incorporación de cambios, proyectos y versiones.
Nota:
La autenticación SAML no es necesaria para colaboradores externos. Para más información sobre los colaboradores externos, consulta Roles en una organización.
If you have recently authenticated with your organization's SAML IdP in your browser, you are automatically authorized when you access a GitHub organization that uses SAML SSO. If you haven't recently authenticated with your organization's SAML IdP in your browser, you must authenticate at the SAML IdP before you can access the organization.
Debes usar periódicamente tu IdP de SAML para autenticarte y obtener acceso a los recursos de la organización de GitHub. Tu IdP especifica la duración de este período de inicio de sesión y, generalmente, es de 24 horas. Este requisito de inicio de sesión periódico limita la duración del acceso y requiere que te vuelvas a identificar para continuar. Puedes ver y administrar tus sesiones de SAML activas en la configuración de seguridad. Para más información, consulta Viewing and managing your active SSO sessions.
Linked external identities
When you authenticate with your IdP account and return to GitHub, GitHub will record a link in the organization or enterprise between your GitHub personal account and the external identity you signed into. This linked identity is used to validate your membership in that organization, and depending on your organization or enterprise setup, is also used to determine which organizations and teams you're a member of as well. Each GitHub account can be linked to exactly one external identity per organization. Likewise, each external identity can be linked to exactly one GitHub account in an organization.
If you sign in with an external identity that is already linked to another GitHub account, you will receive an error message indicating that you cannot sign in with that identity. This situation can occur if you are attempting to use a new GitHub account to work inside of your organization. If you didn't intend to use that external identity with that GitHub account, then you'll need to sign out of that external identity and then repeat the SSO login. If you do want to use that external identity with your GitHub account, you'll need to ask your administrator to unlink your external identity from your old account, so that you can link it to your new account. Depending on the setup of your organization or enterprise, your admin may also need to reassign your identity within your identity provider. For more information, see Visualización y administración del acceso SAML de un miembro a su organización.
If the external identity you sign in with does not match the external identity that is currently linked to your GitHub account, you'll receive a warning that you are about to relink your account. As your external identity is used to govern access and team membership, continuing with the new external identity can cause you to lose access to teams and organizations inside of GitHub. Only continue if you know that you're supposed to use that new external identity for authentication in the future.
Authorizing personal access tokens and SSH keys with SSO
To use the API or Git on the command line to access protected content in an organization that uses SSO, you will need to use an authorized personal access token over HTTPS or an authorized SSH key.
If you don't have a personal access token or an SSH key, you can create a personal access token for the command line or generate a new SSH key. For more information, see Administración de tokens de acceso personal or Generación de una nueva clave SSH y adición al agente SSH.
To use a new or existing personal access token or SSH key with an organization that uses or enforces SSO, you will need to authorize the token or authorize the SSH key for use with the organization. For more information, see Authorizing a personal access token for use with single sign-on or Authorizing an SSH key for use with single sign-on.
About OAuth apps, GitHub Apps, and SSO
You must have an active SSO session each time you authorize an OAuth app or GitHub App in order to access an organization that uses or enforces SSO. If you do not have an active session for an organization that requires SSO when you sign into the app, the app will be unable to access that organization. You can create an active SSO session by navigating to https://github.com/orgs/ORGANIZATION-NAME/sso or https://github.com/enterprises/ENTERPRISE-NAME/sso in your browser.
After an enterprise or organization owner enables or enforces SSO for an organization, and after you authenticate via SSO for the first time, you must reauthorize any OAuth apps or GitHub Apps that you previously authorized to access the organization.
To see the OAuth apps you've authorized, visit your OAuth apps page. To see the GitHub Apps you've authorized, visit your GitHub Apps page.
For more information, see Aplicaciones SAML y GitHub.