shaandClaude Opus 5 f0d7c1f474 traefik-forward-auth: send PKCE code_challenge, default on ...

Pocket ID rejects the authorization request outright when its OIDC client
has PKCE required -- "This client requires PKCE, but the 'code_challenge'
parameter is missing" -- which is the default for clients created in recent
Pocket ID versions. Every app behind the portal fails at login, not just
the one being tested.

Upstream supports this via the pocketID provider's enablePKCE flag; the
chart never emitted it, so it stayed at its false default. Adds it to the
normalised portal shape (per-portal override via portals[].pocketID.enablePKCE)
and defaults it on, since PKCE is harmless when the client does not require it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-22 02:39:14 +03:00

..

_helpers.tpl

traefik-forward-auth: send PKCE code_challenge, default on

2026-09-22 02:39:14 +03:00

configmap.yaml

traefik-forward-auth: send PKCE code_challenge, default on

2026-09-22 02:39:14 +03:00

deployment.yaml

feat(traefik-forward-auth): serve several domains and portals from one instance

2026-08-18 00:10:40 +03:00

ingress.yaml

feat: Add traefik-forward-auth Helm chart with deployment, service, ingress, middleware, and configuration templates

2026-04-19 13:21:22 +03:00

middleware.yaml

feat(traefik-forward-auth): serve several domains and portals from one instance

2026-08-18 00:10:40 +03:00

service.yaml

feat: Add traefik-forward-auth Helm chart with deployment, service, ingress, middleware, and configuration templates

2026-04-19 13:21:22 +03:00