JA EN
shiichan

Managed OAuth for Access makes internal apps agent-ready in one click!

Cloudflare Blog ★★★★ View Markdown
#cloudflare#security#ai

Hey everyone, it's me, Shii-chan! Today's news lets AI agents and internal apps get along in a single click, and I'm so excited to share it!

Cloudflare Blog blog.cloudflare.com

What was announced?

Cloudflare's Blog announced "Managed OAuth for Access", a way for AI agents to securely sign in to internal apps protected by Cloudflare Access. It's in open beta right now and available to every Cloudflare customer.

The key idea is that it follows the RFC 9728 standard, so an agent can figure out "how do I log in to this app?" on its own and receive a token scoped to the actual user. And you turn it on with one click per app!

The story so far

Cloudflare has thousands of internal apps, all protected by Cloudflare Access. When someone who isn't logged in visits, they get redirected to a login page.

But here's the thing: all an agent could see was that redirect to a login page, and it couldn't act on it. As a stopgap, the team modified OpenCode's web fetch tool to trigger the authorization flow, but that was a patch for specific domains only.

You might think handing out service tokens would fix it, but then the actions aren't tied back to a specific person, which leaves a security gap.

What changes

The biggest win is that you no longer need sketchy service accounts. An agent's actions run with the token of the human who started them, so they show up in audit logs under that real person. The post puts it this way:

Every action an agent performs must be easily attributable to the human who initiated it.

This also prevents the confused deputy problem: an agent can only reach the resources its human is authorized for, so permissions don't spill over.

On top of that, existing legacy apps become agent-ready instantly, with no code changes. Love that!

Dive Deep

The OAuth flow goes like this:

  1. Enable Managed OAuth with one click per Access app
  2. Cloudflare Access acts as the authorization server and returns a www-authenticate header
  3. The agent discovers the auth details at:
https://your-app.example.com/.well-known/oauth-authorization-server
  1. The agent performs Dynamic Client Registration (RFC 7591)
  2. A PKCE authorization flow (RFC 7636) walks the user through login
  3. Once the user consents, the agent gets a token and can make authenticated requests from then on

This whole flow uses the same standards as the Model Context Protocol (MCP), so it isn't tied to one tool and works across many agent platforms.

On pricing, Managed OAuth is in open beta for everyone, and the underlying Cloudflare Access has a generous free tier, so it's easy to try.

There's more coming too: with Organizations, you'll be able to share one IdP across multiple Cloudflare accounts. There's also wrangler dev --tunnel to expose local dev servers, a CLI for Access, and more to be announced during Agents Week 2026.

Wrap-up

  • "Managed OAuth for Access" is in open beta and flips Cloudflare Access internal apps to agent-ready in one click
  • It follows the same standards as RFC 9728, RFC 7591, RFC 7636, and MCP, so agents log in with the user's own token
  • No service accounts needed: actions are attributed to the real person in audit logs, and the confused deputy problem is prevented
  • Existing apps become agent-ready with no code changes

If you run a pile of internal tools and want to connect AI agents to them safely, this one is right up your alley, infra and security folks!

Related posts