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://harbor.example.com
  • Authelia Root URL: https://auth.example.com
  • Client ID: harbor
  • Client Secret: harbor_client_secret



To configure Harbor to utilize Authelia as an OpenID Connect Provider:

  1. Visit Administration
  2. Visit Configuration
  3. Visit Authentication
  4. Select OIDC from the Auth Mode drop down
  5. Enter the following information:
    1. OIDC Provider Name: Authelia
    2. OIDC Provider Endpoint: https://auth.example.com
    3. OIDC Client ID: harbor
    4. OIDC Client Secret: harbor_client_secret
    5. Group Claim Name: groups
    6. OIDC Scope: openid,profile,email,groups
    7. For OIDC Admin Group you can specify a group name that matches your authentication backend.
    8. Ensure Verify Certificate is checked.
    9. Ensure Automatic onboarding is checked if you want users to be created by default.
    10. Username Claim: preferred_username
  6. Click Test OIDC Server
  7. Click Save


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

- id: harbor
  secret: harbor_client_secret
  public: false
  authorization_policy: two_factor
    - openid
    - profile
    - groups
    - email
    - https://vault.example.com/oidc/callback
    - https://vault.example.com/ui/vault/auth/oidc/oidc/callback
  userinfo_signing_algorithm: none

See Also