About SCIM

With System for Cross-domain Identity Management (SCIM), administrators can automate the exchange of user identity information between systems.

El inicio de sesión único de SAML se encuentra disponible con GitHub Enterprise Cloud. Para obtener más información, consulta la sección "Productos de GitHub".

If you use SAML SSO in your organization, you can implement SCIM to add, manage, and remove organization members' access to GitHub. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization.

If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM.

These identity providers are compatible with the GitHub SCIM API for organizations. For more information, see SCIM in the GitHub API documentation.

  • Azure AD
  • Okta
  • OneLogin

Si estás participando en el beta privado para el aprovisionamiento de usuario para cuentas empresariales, cuando habilites SAML para tu cuenta empresarial, se habilitará predeterminadamente el aprovisionamiento y desaprovisionamiento de SCIM en GitHub. Puedes utilizar el aprovisionamiento para administrar la membrecía de la organización si configuras SCIM en tu IdP. For more information, see "About user provisioning for organizations in your enterprise account."

Further reading

Did this doc help you?Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

O, learn how to contribute.