Skip to content

Standard

PKCE

Proof Key for Code Exchange (RFC 7636) is an OAuth 2.0 extension that prevents authorization code interception using a secret code verifier.

Known aliases

  • code_challenge
  • PKCE
  • plain code challenge method
  • Proof Key for Code Exchange
  • S256

Current stories

buildOne report1 publisher

Sign in with ChatGPT lets Plus and Pro users cover an app's AI requests from their own plan

OpenAI's Sign in with ChatGPT lets Plus and Pro users run an app's AI requests on their own plan, up to a weekly cap they set per app. That cap reserves none of the user's quota, so builders still need their own API key for any request the plan cannot cover.

Publishers:dev.to

Reality

Evidence55
Adoption30
Hype gap+5
Incentives30
Confidence50
buildOne report1 publisher

QRFLOW.codes traced its MCP OAuth exposure to a consent screen that trusted registrant-chosen names

QRFLOW.codes' developer refused both fixes a security report proposed for open OAuth client registration, saying either would lock Claude and ChatGPT out. The exposure turned out to be a consent screen showing attacker-chosen app names, now handled by trusting redirect hosts.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+10
Incentives50
Confidence50
buildOne report1 publisher

MCP servers need their RFC 9728 resource URL to reject tokens minted for other servers

MCP servers that skip audience binding accept tokens minted for other servers, says a dev.to OAuth 2.1 guide that puts it in the 80% most guides skip. The check depends on RFC 9728 metadata the server publishes and a resource parameter the client sends.

Publishers:dev.to

Reality

Evidence30
Adoption
Not scored
Hype gap+25
Incentives60
Confidence35
buildOne report1 publisher

Six OAuth steps run before an MCP client makes its first tool call

The MCP spec mandates OAuth 2.1 with PKCE, dynamic client registration and metadata discovery for remote servers. The one-hour tokens and customer-facing audit logs procurement asks about come from a guide's own bar.

Publishers:dev.to

Reality

Evidence40
Adoption
Not scored
Hype gap+25
Incentives55
Confidence48
buildOne report1 publisher

A Cloudflare Worker generates the code_challenge IFTTT's redirect leaves out

IFTTT's authorization redirect arrives with no code_challenge, and an authorization server that mandates PKCE answers invalid_request. Publora's developer kept the requirement and put a Cloudflare Worker in front of it.

Publishers:dev.to

Reality

Evidence60
Adoption20
Hype gap−5
Incentives55
Confidence55
buildOne report1 publisher

Sharing an MCP server across a team now costs an OAuth 2.1 authorization flow

The auth overhaul in the final MCP spec reaches only remote transports, which turns a compliance question into a question about deployment topology, and even the vendors credited with getting ahead of it need checking.

Publishers:dev.to

Reality

Evidence38
Adoption45
Hype gap+28
Incentives55
Confidence45
buildOne report1 publisher

A remote MCP server spends five of its six routes on getting the client signed in

The tool logic is one route handler. The other five routes stand up an OAuth authorization server and two well-known documents, and the 401 that points at them decides whether Claude ever shows a sign-in page.

Publishers:dev.to

Reality

Evidence52
Adoption25
Hype gap+8
Incentives55
Confidence58
productOne report1 publisher

A public OIDC client with PKCE replaces the cluster certificate that outlives its owner

Self-hosted Kubernetes still hands out certificate files that keep working after their owner leaves. The fix in a CNCF walkthrough turns on one Keycloak toggle, because a confidential client only moves the shared static credential onto every laptop.

Publishers:cncf.io

Reality

Evidence60
Adoption
Not scored
Hype gap+12
Incentives45
Confidence58
buildOne report1 publisher

authentik checked the PKCE verifier only when the request bothered to include one

One authentik CVE covers a token endpoint accepting a missing code_verifier; another, six months later, covers an authorization endpoint accepting a missing code_challenge. OpenAM's equivalent check ships switched off.

Publishers:dev.to

Reality

Evidence60
Adoption45
Hype gap+15
Incentives20
Confidence55
buildOne report1 publisher

Keycloak's metadata-document executor provisions clients that accept plain PKCE

The S256 pin is a per-client attribute, and the executor that builds a client from a published metadata document sets three attributes, all unrelated to PKCE. The executor addition imports cleanly, yet it never runs.

Publishers:dev.to

Reality

Evidence58
Adoption12
Hype gap−12
Incentives22
Confidence52
buildOne report1 publisher

Once an agent can write, the wrong post looks exactly like the right one

An MCP server for social publishing shipped OAuth, sixteen tools and six destructive flags. The failures that actually hurt still come back as ordinary successes.

Publishers:dev.to

Reality

Evidence42
Adoption16
Hype gap+8
Incentives72
Confidence55
buildOne report1 publisher

Agents fit neither IAM model, so the bill lands on per-step tokens and an intent authority

A New Stack prescription lists six identity capabilities for autonomous agents. The useful part is which old assumption each one retires, and what per-step credentials cost to run.

Publishers:thenewstack.io

Reality

Evidence28
Adoption
Not scored
Hype gap+42
Incentives58
Confidence46
buildOne report1 publisher

Atlas App Connections hands AI clients your whole Atlas role, so fix the roles first

MongoDB's OAuth 2.1 platform issues tokens that call the Atlas Administration API with the authorizing user's full permissions. Least-privilege role design stops being hygiene and becomes the control.

Publishers:mongodb.com

Reality

Evidence76
Adoption15
Hype gap−5
Incentives62
Confidence63
buildOne report1 publisher

Cognito rejects RFC 8707, so it cannot be the authorization server for an MCP client

A dev.to writeup documents Amazon Cognito killing a spec-compliant MCP connector at the first redirect, and the only fix on offer is a proxy that strips one parameter and nothing else.

Publishers:dev.to

Reality

Evidence46
Adoption18
Hype gap−6
Incentives30
Confidence44