implicit grant
An old OAuth flow that returned access tokens directly in the browser redirect, now deprecated because tokens could leak.
Tokens delivered in the redirect URL can leak through history, logs and referrer headers.
In more detail
Tokens in a URL end up in browser history, logs and referrer headers. Current guidance is to use the authorization code flow with PKCE instead, even for browser apps.
Related terms
- authorization code flow — The OAuth flow in which the browser brings back a short-lived code that the client then exchanges directly with the authorization server for tokens.
- PKCE — Short for Proof Key for Code Exchange: the client sends a hash of a random secret at the start of the flow and the secret itself when exchanging the code.
- OAuth 2.0 — A framework for delegated authorization: a user lets an application call an API on their behalf without giving it their password.
Taught in
- OAuth2 & OpenID Connect: Social Auth & PKCE Flows — Production Full-Stack Engineering