Automation 360 supports OAuth Dynamic Client Registration (DCR) for Automation 360 Cloud deployments, which enables applications to programmatically register as OAuth clients with the Automation 360 server.
Dynamic Client Registration eliminates the need to manually create an OAuth client in Control Room, making it useful for applications such as MCP clients.
Dynamically registered OAuth clients can use supported OAuth flows, such as Authorization Code with PKCE, to obtain authorization to access Automation 360 resources.
Before you begin
- Application Registration View – to view existing OAuth clients.
- Application Registration Manage – to create, update, and delete OAuth clients.
Automation 360 Dynamic Client Registration workflow
When using Dynamic Client Registration:
- The user provides the Automation 360 Dynamic
Client Registration endpoint URL. For example:
https://<your-control-room-url>/mcp. - The client application sends the required registration metadata to this endpoint
on behalf of the user. The client sets the metadata, which includes fields such
as:
- Client/application name
- Redirect URI
- Supported grant type
- Response type
Note: Some client applications allow users to configure certain metadata fields before registration. Refer to your client application's documentation for details. - Automation 360 server validates the registration request.
- Automation 360 registers the OAuth client and returns the required client
information and metadata.Note: Store client credentials or other sensitive information returned during registration securely.
All clients registered using DCR can be viewed and managed on the page. See View and manage OAuth clients.
After successfully registering the client, the OAuth client can access the permitted Automation 360 resources using the supported OAuth authorization flow.