Skip to content
AuthAction Documentation

Dynamic Client Registration (DCR)

Dynamic Client Registration (DCR) allows applications to register themselves with AuthAction without manual configuration in the dashboard. This is useful for MCP (Model Context Protocol) servers, developer tools, and scenarios where clients need to onboard dynamically.

Overview

Section titled “Overview”

With DCR enabled:

  • Applications can register via the POST /oauth2/register endpoint.
  • Registered clients receive a Client ID and can obtain tokens for configured API servers.
  • You control which authentication connections are available to dynamically registered clients.

Enabling DCR

Section titled “Enabling DCR”
  1. Open the AuthAction Dashboard.
  2. Navigate to Settings > Advanced.
  3. Enable Dynamic Client Registration.

When enabled, any client can call the registration endpoint. Restrict this to trusted environments in production.

Registration Flow

Section titled “Registration Flow”
  1. Client sends a registration request to POST https://<tenant>.<region>.authaction.com/oauth2/register.
  2. AuthAction creates the application and returns client credentials.
  3. Client uses the credentials to obtain tokens and access allowed API resources.

API Server Access

Section titled “API Server Access”

For dynamically registered clients to access an API server (e.g. MCP API):

  1. Go to Applications > APIs.
  2. Select the API server.
  3. Open the Dynamic Clients tab.
  4. Enable Dynamic Client Access.
Section titled “Related”