Skip to content

mbp-1043: gate client_id injection on Entra ID provider#157

Open
p-rog wants to merge 1 commit into
validatedpatterns:mainfrom
p-rog:mbp-1043
Open

mbp-1043: gate client_id injection on Entra ID provider#157
p-rog wants to merge 1 commit into
validatedpatterns:mainfrom
p-rog:mbp-1043

Conversation

@p-rog

@p-rog p-rog commented Jul 17, 2026

Copy link
Copy Markdown
Collaborator

Problem: The qtodo AzureClientIdRequestFilter fires unconditionally, breaking Keycloak OIDC authentication with a "client_id parameter does not match sub claim" error. The filter is only needed for Azure Entra ID, where the OIDC provider requires client_id alongside client_assertion.

Fix: Set QTODO_OIDC_INJECT_CLIENT_ID=true in the qtodo ConfigMap only when .Values.app.oidc.provider is "entraid". Keycloak deployments (the default) are unaffected — the env var is not set, and the filter defaults to inactive.

Changed file:
• charts/qtodo/templates/app-config-env.yaml — added QTODO_OIDC_INJECT_CLIENT_ID: "true" inside the existing {{- if eq .Values.app.oidc.provider "entraid" }} block

Depends on: validatedpatterns-demos/qtodo#9

The AzureClientIdRequestFilter in qtodo unconditionally injects
client_id into OIDC token exchange requests. This breaks Keycloak's
federated-jwt authenticator because it requires client_id to match
the JWT sub claim (the SPIFFE ID), not the OIDC client ID.

Set QTODO_OIDC_INJECT_CLIENT_ID=true only when the OIDC provider is
entraid, keeping the filter inactive for Keycloak deployments.

Depends-on: validatedpatterns-demos/qtodo (AzureClientIdRequestFilter
must read qtodo.oidc.inject-client-id, defaulting to false)

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant