2.6 KiB
2.6 KiB
title | description | lead | date | draft | images | menu | weight | toc | community | aliases | |||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Portainer | Integrating Portainer with Authelia via OpenID Connect. | 2022-05-15T13:52:27+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://portainer.example.com
- Authelia Root URL:
https://auth.example.com
- Client ID:
portainer
- Client Secret:
portainer_client_secret
Configuration
Application
To configure Portainer to utilize Authelia as an OpenID Connect Provider:
- Visit Settings
- Visit Authentication
- Select:
- Authentication Method: OAuth
- Provider: Custom
- Enable Automatic User Provision if you want users to automatically be created in Portainer.
- Configure the following:
- Client ID:
portainer
- Client Secret:
portainer_client_secret
- Authorization URL:
https://auth.example.com/api/oidc/authorization
- Access Token URL:
https://auth.example.com/api/oidc/token
- Resource URL:
https://auth.example.com/api/oidc/userinfo
- Redirect URL:
https://portainer.example.com
- User Identifier:
preferred_username
- Scopes:
openid profile groups email
- Client ID:
{{< figure src="portainer.png" alt="Portainer" width="736" style="padding-right: 10px" >}}
Authelia
The following YAML configuration is an example Authelia client configuration for use with Portainer which will operate with the above example:
- id: portainer
secret: portainer_client_secret
public: false
authorization_policy: two_factor
scopes:
- openid
- profile
- groups
- email
redirect_uris:
- https://portainer.example.com
userinfo_signing_algorithm: none