PulseAugur
EN
LIVE 13:37:46

Keycloak 26.7.1 CIMD feature fails to provision PKCE-pinned clients

By PulseAugur Editorial · [1 sources] ·

A user encountered an issue with Keycloak 26.7.1 where a provisioned OAuth client, created via the Client ID Metadata Document (CIMD) feature, did not inherit the expected PKCE (Proof Key for Code Exchange) pin. Despite the realm's configuration enforcing PKCE with the S256 method for manually created clients, the CIMD-provisioned client accepted requests without a PKCE challenge or with a plain method. The problem stems from the CIMD provider not including PKCE attributes during client provisioning, and the PKCE enforcer executor not being triggered by the relevant event in the client ID URI condition. AI

RANK_REASON The item describes a specific bug or unexpected behavior in a software product (Keycloak) related to its configuration and feature interaction, rather than a new release or major industry development.

Read on dev.to — MCP tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Keycloak 26.7.1 CIMD feature fails to provision PKCE-pinned clients

How we ranked this

Signal score
4 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
The item describes a specific bug or unexpected behavior in a software product (Keycloak) related to its configuration and feature interaction, rather than a new release or major industry development.
Source corroboration
Single-source cluster
Only one publisher covered this so far. Single-source stories can still rank when the publisher is high-authority, but they lack cross-source corroboration.
Topics
product, other
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
Low
Off-topic or adjacent — cluster remains reachable but doesn't surface in AI-industry rankings.
Story freshness
Breaking (< 6h)
Fresh story with cross-source coverage still developing. Ranking may shift as more sources report.

Full methodology in our editorial standards.

COVERAGE [1]

  1. dev.to — MCP tag TIER_1 English(EN) · Marcos Sousa ·

    A provisioned Keycloak client inherits no PKCE pin, and the obvious fix is inert

    <p>Keycloak 26.7.1, in a realm where every hand-authored client carries <code>"pkce.code.challenge.method": "S256"</code> and refuses <code>plain</code>. Enable the OAuth Client ID Metadata Document feature, point an authorization request at a published metadata document as its <…

RELATED ENTITIES

RELATED TOPICS