2022-06-15 07:51:47 +00:00
---
title: "Harbor"
2022-07-01 03:07:02 +00:00
description: "Integrating Harbor with the Authelia OpenID Connect Provider."
2022-06-15 07:51:47 +00:00
lead: ""
2022-06-28 05:27:14 +00:00
date: 2022-06-15T17:51:47+10:00
2022-06-15 07:51:47 +00:00
draft: false
images: []
menu:
integration:
parent: "openid-connect"
weight: 620
toc: true
community: true
---
## Tested Versions
* [Authelia]
* [v4.35.5 ](https://github.com/authelia/authelia/releases/tag/v4.35.5 )
* [Harbor]
* 2.5.0
## Before You Begin
2023-02-02 01:30:06 +00:00
{{% oidc-common %}}
2022-10-20 04:42:22 +00:00
2022-10-20 04:27:09 +00:00
### Assumptions
2022-06-15 07:51:47 +00:00
This example makes the following assumptions:
* __Application Root URL:__ `https://harbor.example.com`
* __Authelia Root URL:__ `https://auth.example.com`
* __Client ID:__ `harbor`
2023-02-02 01:30:06 +00:00
* __Client Secret:__ `insecure_secret`
2022-06-15 07:51:47 +00:00
## Configuration
### Application
2023-01-25 23:59:18 +00:00
To configure [Harbor] to utilize Authelia as an [OpenID Connect 1.0] Provider:
2022-06-15 07:51:47 +00:00
1. Visit Administration
2. Visit Configuration
3. Visit Authentication
4. Select `OIDC` from the `Auth Mode` drop down
2022-07-01 03:07:02 +00:00
5. Set the following values:
2022-06-15 07:51:47 +00:00
1. OIDC Provider Name: `Authelia`
2. OIDC Provider Endpoint: `https://auth.example.com`
3. OIDC Client ID: `harbor`
2023-02-02 01:30:06 +00:00
4. OIDC Client Secret: `insecure_secret`
2022-06-15 07:51:47 +00:00
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__
2023-05-15 00:32:10 +00:00
[client configuration ](../../../configuration/identity-providers/openid-connect/clients.md ) for use with [Harbor]
2022-06-15 07:51:47 +00:00
which will operate with the above example:
```yaml
2023-04-02 03:12:01 +00:00
identity_providers:
oidc:
## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
## See: https://www.authelia.com/c/oidc
clients:
2023-05-07 06:39:17 +00:00
- id: 'harbor'
description: 'Harbor'
2023-04-02 03:12:01 +00:00
secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng' # The digest of 'insecure_secret'.
public: false
2023-05-07 06:39:17 +00:00
authorization_policy: 'two_factor'
2023-04-02 03:12:01 +00:00
redirect_uris:
2023-05-07 06:39:17 +00:00
- 'https://harbor.example.com/c/oidc/callback'
2023-04-02 03:12:01 +00:00
scopes:
2023-05-07 06:39:17 +00:00
- 'openid'
- 'profile'
- 'groups'
- 'email'
2023-05-15 00:32:10 +00:00
userinfo_signing_alg: 'none'
2022-06-15 07:51:47 +00:00
```
## See Also
* [Harbor OpenID Connect Provider Documentation ](https://goharbor.io/docs/2.5.0/administration/configure-authentication/oidc-auth/ )
[Authelia]: https://www.authelia.com
[Harbor]: https://goharbor.io/
2023-01-25 23:59:18 +00:00
[OpenID Connect 1.0]: ../../openid-connect/introduction.md