Vibeleaderboard
← All Intel
Intel / blog

From all-or-nothing to task-based OAuth consent

Source
blog.cloudflare.com
Date

Context

Cloudflare's OAuth consent change lets users refuse selected permissions without rejecting an entire application connection. Developers must first mark those permissions as optional. When an application requests them, the user can deselect them on the consent screen; required permissions within that request remain necessary. Cloudflare's explanation says the default still approves the full requested set.

The application must then check what access it actually received. An granted fewer permissions has to operate within that smaller set, rather than assume every requested operation is authorized. This makes narrower access possible within one connection flow, provided the developer supports optional permissions and handles partial approval. The implementation guidance explicitly requires checking the granted scope set.

Terms in this piece · Glossary
  • AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
  • MCP — The Model Context Protocol — an open standard that lets any AI assistant plug into any tool or data source without custom integration code.
Read the source blog.cloudflare.com
Recommended reads
Comments

Checking sign-in…

Loading comments…