This documentation is maintained by the community, it is not guaranteed to be complete or up-to-date. We always recommend users read the third-party documentation as part of the integration process to ensure the configuration matches their needs and as such we always link the documentation if available. If you find an error in this documentation please either start a Discussion, make a Pull Request, or contact us on a Chat Room.
Before You Begin
- You are required to utilize a unique client id for every client.
- The client id on this page is merely an example and you can theoretically use any alphanumeric string.
- You should not use the client secret in this example, We strongly recommend reading the Generating Client Secrets guide instead.
This example makes the following assumptions:
- Application Root URL:
- Authelia Root URL:
- Client ID:
- Client Secret:
- CLI Client ID:
To configure Argo CD to utilize Authelia as an OpenID Connect 1.0 Provider use the following configuration:
name: Authelia issuer: https://auth.example.com clientID: argocd clientSecret: argocd_client_secret cliClientID: argocd-cli requestedScopes: - openid - profile - email - groups
The following YAML configuration is an example Authelia client configuration for use with Argo CD which will operate with the above example:
- id: argocd description: Argo CD secret: '$plaintext$argocd_client_secret' public: false authorization_policy: two_factor redirect_uris: - https://argocd.example.com/auth/callback scopes: - openid - groups - email - profile userinfo_signing_algorithm: none - id: argocd-cli description: Argo CD (CLI) public: true authorization_policy: two_factor redirect_uris: - http://localhost:8085/auth/callback scopes: - openid - groups - email - profile - offline_access userinfo_signing_algorithm: none