2.7 KiB
2.7 KiB
title | description | lead | date | draft | images | menu | weight | toc | community | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Harbor | Integrating Harbor with the Authelia OpenID Connect Provider. | 2022-06-15T17:51:47+10:00 | false |
|
620 | true | true |
Tested Versions
Before You Begin
Common Notes
- You are required to utilize a unique client id for every client.
- The client id on this page is merely an example and you can theoretically use any alphanumeric string.
- 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:
- Visit Administration
- Visit Configuration
- Visit Authentication
- Select
OIDC
from theAuth Mode
drop down - Set the following values:
- OIDC Provider Name:
Authelia
- OIDC Provider Endpoint:
https://auth.example.com
- OIDC Client ID:
harbor
- OIDC Client Secret:
harbor_client_secret
- Group Claim Name:
groups
- OIDC Scope:
openid,profile,email,groups
- For OIDC Admin Group you can specify a group name that matches your authentication backend.
- Ensure
Verify Certificate
is checked. - Ensure
Automatic onboarding
is checked if you want users to be created by default. - Username Claim:
preferred_username
- OIDC Provider Name:
- Click
Test OIDC Server
- 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