2.5 KiB
2.5 KiB
title | description | lead | date | draft | images | menu | weight | toc | community | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Harbor | Integrating Harbor with Authelia via OpenID Connect. | 2022-05-16T21:44:13+10:00 | false |
|
620 | true | true |
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
Configuration
Application
To configure Harbor to utilize Authelia as an OpenID Connect Provider:
- Visit Administration
- Visit Configuration
- Visit Authentication
- Select
OIDC
from theAuth Mode
drop down - Enter the following information:
- 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
secret: harbor_client_secret
public: false
authorization_policy: two_factor
scopes:
- openid
- profile
- groups
- email
redirect_uris:
- https://vault.example.com/oidc/callback
- https://vault.example.com/ui/vault/auth/oidc/oidc/callback
userinfo_signing_algorithm: none