Replies: 2 comments 2 replies
|
Had another look and you had a point, so env support is going into 1.13.0. All ten OIDC fields: environment:
- OIDC_ENABLED=true
- OIDC_PROVIDER_URL=https://id.example.com/application/o/tm/
- OIDC_CLIENT_ID=traefik-manager
- OIDC_CLIENT_SECRET=your-client-secret
- OIDC_DISPLAY_NAME=Authentik
- OIDC_ALLOWED_EMAILS=
- OIDC_ALLOWED_GROUPS=admins
- OIDC_GROUPS_CLAIM=groups
- OIDC_ALLOW_ANY_AUTHENTICATED=false
- OIDC_AUTO_LOGIN=falseSame rule as |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
What problem does this solve?
Traefik Manager currently supports OIDC, but it must first be configured through the UI after logging in with local authentication. For automated/self-hosted deployments, this means the initial deployment is not fully declarative, a local password still needs to be created and stored, followed by manual OIDC setup through the UI.
Proposed solution
Allow OIDC to be configured directly through environment variables, including things like the issuer/discovery URL, client ID/secret, scopes, redirect URL.
This would make OIDC usable right from the first startup, without having to create/store a local password and then configure OIDC manually through the UI.
A few benefits:
The existing UI configuration could remain as-is, with environment variables taking precedence when provided.
Which area does this relate to?
Authentication / Security
All reactions