Argo CD SSO integrations

Connecting Argo CD to specific identity providers through direct OIDC or bundled Dex, and turning their groups into Argo CD roles for people and automation.

Argo CD SSO with Microsoft Entra ID

Signing in to Argo CD with Microsoft Entra ID: direct OIDC with workload identity instead of a client secret, SAML or the microsoft connector through Dex, group claims mapped to RBAC, and the 200-group overage problem.

Argo CD SSO with Okta

Connecting Argo CD to Okta: direct OIDC with a custom authorization server and a groups claim, the separate CLI client, SAML through Dex when the groups claim is not available, and mapping Okta groups to roles.

Argo CD SSO with Google Workspace and Google Groups

Using Google accounts for Argo CD sign-in through Dex: plain OIDC without groups, the Dex google connector with a domain-wide delegated service account for group-based RBAC, and why SAML is not recommended.

Argo CD with LDAP or Active Directory through Dex

Authenticating Argo CD users against LDAP or Active Directory with the Dex LDAP connector when no OIDC provider exists: bind settings, group search for RBAC, TLS to the directory, and when to front the directory with an IdP instead.

Argo CD SSO with Auth0

Connecting Argo CD to Auth0 with OIDC: application settings, adding a groups or roles claim with an Auth0 action, callback and logout URLs, and mapping the claim to Argo CD RBAC.

Argo CD CLI single sign-on and PKCE

Making argocd login --sso work behind your identity provider: the CLI client ID and localhost callback, PKCE settings, the server-side callback since 3.1, logout URLs, and fixes for common redirect errors.

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.