All 29 RBAC questions
More in RBAC
What is the exec resource in RBAC and why is it sensitive? What actions can be controlled for the applications resource? What resources can ArgoCD RBAC control besides applications? How do you create a read-only role scoped to one project? How do you manage RBAC declaratively under GitOps? How do you restrict which repositories a project can use? How do you prevent a team from deploying to namespaces they don't own? What permissions are needed to manage ApplicationSets? How do AppProjects and RBAC work together for multi-tenancy? How do you grant fine-grained permissions like sync but not delete?
Advertisement
Back to results for “Applications”
ArgoCD › RBAC

What is a local account and when would you use one?

Intermediate

Answer

Local accounts are ArgoCD-managed users (defined in argocd-cm) with passwords or tokens, used for automation or break-glass access when SSO is unavailable. They should be limited and carefully permissioned; SSO is preferred for humans, local accounts for specific service/automation needs.
# argocd-cm
data:
  accounts.ci-bot: apiKey
Real-world example A ci-bot local account issues an API token for the pipeline, separate from human SSO logins.

Common follow-ups: When are local accounts appropriate? | Why prefer SSO for humans?

Applications Multi-cluster RBAC
All 29 RBAC questions