By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

PKCE and native app flows

Agents are public clients that cannot keep a secret, so they rely on PKCE to bind an authorization code to the client that started the flow. Native app guidance covers loopback redirects and system browsers, and the device grant handles headless machines. MCP requires clients to implement PKCE and to confirm the authorization server supports it.

Read in this order

  1. OfficialRFC 7636: Proof Key for Code ExchangeStart here: how PKCE stops a stolen authorization code from being redeemed.
  2. OfficialRFC 8252: OAuth 2.0 for Native AppsRedirect and browser rules for apps that run on a user's machine.
  3. OfficialRFC 8628: OAuth 2.0 Device Authorization GrantThe device flow for agents on machines without a browser.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.