Portainer

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:

  1. Visit Settings
  2. Visit Authentication
  3. Select:
    1. Authentication Method: OAuth
    2. Provider: Custom
    3. Enable Automatic User Provision if you want users to automatically be created in Portainer.
  4. Configure the following:
    1. Client ID: portainer
    2. Client Secret: portainer_client_secret
    3. Authorization URL: https://auth.example.com/api/oidc/authorization
    4. Access Token URL: https://auth.example.com/api/oidc/token
    5. Resource URL: https://auth.example.com/api/oidc/userinfo
    6. Redirect URL: https://portainer.example.com
    7. User Identifier: preferred_username
    8. Scopes: openid profile groups email
Portainer

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

See Also