Cloud Foundry · OAuth Scopes

Cloud Foundry OAuth Scopes

OAuth 2.0 searched

Cloud Foundry publishes 7 OAuth 2.0 scopes via the implicit flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Cloud Foundry API on a user’s behalf.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

Cloud Foundry FoundationContainersMulti-CloudOpen-SourcePlatform-as-a-ServicePlatform

Scopes: 7 Flows: implicit Method: searched

OAuth endpoints

Authorization URL
https://uaa.cloudfoundry.local/api-oauth/dialog

Flows
implicit

Scopes (7)

Scope	Description	Flows
cloud_controller.admin	This scope provides read and write access to all resources	implicit
cloud_controller.admin_read_only	This scope provides read only access to all resources	implicit
cloud_controller.global_auditor	This scope provides read access to all resources	implicit
cloud_controller.read	Read access to the Cloud Controller	implicit
cloud_controller.update_build_state	This scope allows its bearer to update the state of a build; currently only used when updating builds	implicit
cloud_controller.write	Write access to the Cloud Controller	implicit
cloud_controller_service_permissions.read	This scope provides read only access for service instance permissions	implicit

📄 Provider scope reference: https://docs.cloudfoundry.org/uaa/https://docs.cloudfoundry.org/concepts/roles.html

Source

OAuth Scopes

generated: '2026-09-05'
method: searched
source: openapi/cloud-foundry-capi-v3-openapi.yaml components.securitySchemes.oauth, enriched from https://docs.cloudfoundry.org/concepts/architecture/uaa.html
  and https://docs.cloudfoundry.org/uaa/
schemes:
- name: oauth
  source: openapi/cloud-foundry-capi-v3-openapi.yaml
  flows:
  - flow: implicit
    authorizationUrl: https://uaa.cloudfoundry.local/api-oauth/dialog
scopes:
- scope: cloud_controller.admin
  description: This scope provides read and write access to all resources
  flows:
  - implicit
  sources:
  - openapi/cloud-foundry-capi-v3-openapi.yaml
- scope: cloud_controller.admin_read_only
  description: This scope provides read only access to all resources
  flows:
  - implicit
  sources:
  - openapi/cloud-foundry-capi-v3-openapi.yaml
- scope: cloud_controller.global_auditor
  description: This scope provides read access to all resources
  flows:
  - implicit
  sources:
  - openapi/cloud-foundry-capi-v3-openapi.yaml
- scope: cloud_controller.read
  description: Read access to the Cloud Controller
  flows:
  - implicit
  sources:
  - openapi/cloud-foundry-capi-v3-openapi.yaml
- scope: cloud_controller.update_build_state
  description: This scope allows its bearer to update the state of a build; currently only used when updating builds
  flows:
  - implicit
  sources:
  - openapi/cloud-foundry-capi-v3-openapi.yaml
- scope: cloud_controller.write
  description: Write access to the Cloud Controller
  flows:
  - implicit
  sources:
  - openapi/cloud-foundry-capi-v3-openapi.yaml
- scope: cloud_controller_service_permissions.read
  description: This scope provides read only access for service instance permissions
  flows:
  - implicit
  sources:
  - openapi/cloud-foundry-capi-v3-openapi.yaml
docs:
- https://docs.cloudfoundry.org/uaa/
- https://docs.cloudfoundry.org/concepts/roles.html
note: 'Scopes are issued by the target foundation''s UAA and are read verbatim from the Cloud Foundry Foundation''s
  own CAPI OpenAPI. THE SCOPE IS ONLY HALF THE AUTHORIZATION. Cloud Foundry authorizes on two axes: a UAA scope
  gates the VERB, and a Cloud Foundry ROLE on the target organization or space gates the OBJECT. A token carrying
  cloud_controller.write still gets 403 on a space where the user has no role. The roles (org manager, org auditor,
  org billing manager, space developer, space manager, space auditor, space supporter) are Cloud Controller data,
  not UAA scopes, and appear nowhere in the securitySchemes block — which is why a client built purely from the
  spec''s scope list will misdiagnose its own 403s. The authorizationUrl above (uaa.cloudfoundry.local) is a placeholder:
  the real value is uaa.<system-domain> for the foundation you are calling.'
authorization_model:
  axes:
  - UAA OAuth 2.0 scope (verb)
  - Cloud Foundry role on org/space (object)
  roles:
  - organization_manager
  - organization_auditor
  - organization_billing_manager
  - organization_user
  - space_developer
  - space_manager
  - space_auditor
  - space_supporter
  roles_api: listRoles / createRole (GET,POST /v3/roles) in openapi/cloud-foundry-capi-v3-openapi.yaml
  note: Role assignment is itself an API surface — the Roles tag carries 4 operations.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/cloud-foundry-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.