Tested Versions

Before You Begin

Common Notes

  1. The OpenID Connect 1.0 client_id parameter:
    1. This must be a unique value for every client.
    2. The value used in this guide is merely for demonstration purposes and you can theoretically use nearly any alphanumeric string.
  2. The OpenID Connect 1.0 secret parameter:
    1. The value used in this guide is merely for demonstration purposes and you should absolutely not use this in production and should instead utilize the How Do I Generate Client Secrets FAQ.
    2. This string may be stored as plaintext in the Authelia configuration but this behaviour is deprecated and is not guaranteed to be supported in the future. See the Plaintext guide for more information.
  3. The Configuration example for Authelia is only a portion of the required configuration and it should be used as a guide in conjunction with the standard OpenID Connect 1.0 Configuration guide.


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: insecure_secret



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

  1. Visit Administration
  2. Visit Configuration
  3. Visit Authentication
  4. Select OIDC from the Auth Mode drop down
  5. Set the following values:
    1. OIDC Provider Name: Authelia
    2. OIDC Provider Endpoint: https://auth.example.com
    3. OIDC Client ID: harbor
    4. OIDC Client Secret: insecure_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:

    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
    ## See: https://www.authelia.com/c/oidc
    - id: harbor
      description: Harbor
      secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
      public: false
      authorization_policy: two_factor
        - https://harbor.example.com/c/oidc/callback
        - openid
        - profile
        - groups
        - email
      userinfo_signing_algorithm: none

See Also