Harbor

Tested Versions#

• Authelia
  • v4.38.0
• Harbor
  • 2.5.0

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 readability and demonstration purposes and you should not use this value in production and should instead utilize the How do I generate a client identifier or client secret? FAQ. We recommend 64 random characters but you can use any arbitrary value that meets the other criteria.
   3. This must only contain RFC3986 Unreserved Characters.
   4. This must be no more than 100 characters in length.
2. The OpenID Connect 1.0 client_secret parameter:
   1. The value used in this guide is merely for demonstration purposes and you should absolutely not use this value in production and should instead utilize the How do I generate a client identifier or client secret? 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. When the secret is stored in hashed form in the Authelia configuration (heavily recommended), the cost of hashing can, if too great, cause timeouts for clients. See the Tuning the work factors guide for more information.
3. The configuration example for Authelia:
   1. Only contains an example configuration for the client registration and you MUST also configure the required elements from the OpenID Connect 1.0 Provider Configuration guide.
   2. Only contains a small portion of all of the available options for a registered client and users may wish to configure portions that are not part of this guide or configure them differently, as such it’s important to both familiarize yourself with the other options available and the effect of each of the options configured in this section by looking at the OpenID Connect 1.0 Clients Configuration guide.

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

Some of the values presented in this guide can automatically be replaced with documentation variables.

Set Documentation Variables

Configuration#

Authelia#

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

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

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

See Also#

• Harbor OpenID Connect Provider Documentation