Harbor

Tested Versions #

• Authelia
  • v4.35.5
• Harbor
  • 2.5.0

Before You Begin #

Common Notes #

1. You are required to utilize a unique client id for every client.
2. The client id on this page is merely an example and you can theoretically use any alphanumeric string.
3. You should not use the client secret in this example, We strongly recommend reading the Generating Client Secrets guide instead.

Assumptions #

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

Configuration #

Application #

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

Authelia #

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

- id: harbor
  description: Harbor
  secret: '$plaintext$harbor_client_secret'
  public: false
  authorization_policy: two_factor
  redirect_uris:
    - https://harbor.example.com/c/oidc/callback
  scopes:
    - openid
    - profile
    - groups
    - email
  userinfo_signing_algorithm: none

See Also #

• Harbor OpenID Connect Provider Documentation