RPJosh
/
authelia
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
authelia/docs/content/en/integration/openid-connect/argocd/index.md

2.2 KiB
Raw Blame History

title description lead date draft images menu weight toc community
ArgoCD Integrating ArgoCD with the Authelia OpenID Connect Provider. 2022-07-13T03:42:47+10:00 false
integration
parent
openid-connect
620 true true

Tested Versions

Before You Begin

You are required to utilize a unique client id and a unique and random client secret for all OpenID Connect relying parties. You should not use the client secret in this example, you should randomly generate one yourself. You may also choose to utilize a different client id, it's completely up to you.

This example makes the following assumptions:

  • Application Root URL: https://argocd.example.com
  • Authelia Root URL: https://auth.example.com
  • Client ID: argocd
  • CLI Client ID: argocd-cli
  • Client Secret: argocd_client_secret

Configuration

Application

To configure ArgoCD to utilize Authelia as an OpenID Connect Provider use the following configuration:

name: Authelia
issuer: https://auth.example.com
clientID: argocd
cliClientID: argocd-cli
clientSecret: argocd_client_secret
requestedScopes:
  - openid
  - profile
  - email
  - groups

Authelia

The following YAML configuration is an example Authelia client configuration for use with ArgoCD which will operate with the above example:

- id: argocd
  description: ArgoCD
  redirect_uris:
    - https://argocd.example.com/auth/callback
  scopes:
    - openid
    - groups
    - email
    - profile
  secret: argocd_client_secret
  userinfo_signing_algorithm: none
- description: ArgoCD CLI
  id: argocd-cli
  public: true
  redirect_uris:
    - http://localhost:8085/auth/callback
  scopes:
    - openid
    - groups
    - email
    - profile
  userinfo_signing_algorithm: none

See Also