Cloudflare opens self-managed OAuth applications to all customers

Cloudflare said on 24 June that any customer could create an OAuth application for integrations with its platform. Previously, third-party OAuth was available through a small set of manually onboarded partners. The company described clearer consent, visible application ownership and dashboard revocation as part of opening access more widely.

The announcement also documented the underlying OAuth engine upgrade. Cloudflare preserved revocation events during a database transition so an application whose access had been removed would not regain it after the switch. The company reported fixing session and refresh-token problems during that work. For an integration developer, the release offers a standard delegated-access route; the requested permissions and the ability to withdraw access remain central parts of what the user authorises.