GitLab authentication and user management

Connecting self-managed GitLab to corporate identity: SAML with Entra ID, Okta or Google, LDAP group sync, SCIM provisioning and enforced two-factor authentication.

GitLab SAML SSO with Microsoft Entra ID

Configuring self-managed GitLab as a SAML app in Entra ID: mapping Entra fields to gitlab.rb settings, the certificate thumbprint, group claims for admin and external users, and pairing it with SCIM.

GitLab SAML SSO with Okta

Setting up Okta SAML for self-managed GitLab: the app settings GitLab documents, required groups to restrict sign-in, group attributes for admin and auditor roles and Okta SCIM provisioning.

GitLab SAML SSO with Google Workspace

Signing in to self-managed GitLab with Google Workspace SAML: the custom SAML app, the certificate fingerprint, name ID format and what Google Workspace cannot provision without SCIM.

Troubleshooting blocked LDAP users in GitLab

Why GitLab blocks LDAP users after directory outages or rate limits, how ldap_blocked state clears, resyncing single users and setting up monitoring so a directory hiccup does not lock everyone out.

GitLab SAML admin, auditor and external groups

Controlling GitLab administrator, auditor and external user status from SAML group attributes, where the settings must live in gitlab.rb, and what happens when the groups attribute is missing.

Talk to our team.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.

  • 30-minute call: free, with no obligation.
  • NDA on request: we can sign before you share details.
  • Clear next steps: a scope and plan after the call.