Microcks · OAuth Scopes

Microcks OAuth Scopes

OAuth 2.0 derived

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

Tokens are issued from https://keycloak.example.com/realms/microcks/protocol/openid-connect/token.

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.

API TestingCloud NativeDevOpsMockingOpen Source

Scopes: 3 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://keycloak.example.com/realms/microcks/protocol/openid-connect/token

Flows
clientCredentials

Scopes (3)

Scope	Description	Flows
admin	Administrator of the Microcks instance	clientCredentials
manager	Services & APIs content manager	clientCredentials
user	Simple authenticated user	clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/microcks-openapi.yml
schemes:
- name: jwt-bearer
  source: openapi/microcks-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://keycloak.example.com/realms/microcks/protocol/openid-connect/token
  description: JWT Bearer acquired using OAuth 2 Authentication flow or Direct Access Grant
scopes:
- scope: admin
  description: Administrator of the Microcks instance
  flows:
  - clientCredentials
  sources:
  - openapi/microcks-openapi.yml
- scope: manager
  description: Services & APIs content manager
  flows:
  - clientCredentials
  sources:
  - openapi/microcks-openapi.yml
- scope: user
  description: Simple authenticated user
  flows:
  - clientCredentials
  sources:
  - openapi/microcks-openapi.yml