Automation 360 Control Room can act as an OAuth 2.0 and OpenID Connect (OIDC) Authorization Server for Automation 360 Cloud deployments. Administrators can register up to 25 external OAuth clients per Control Room and manage their lifecycle and access permissions.
After registration, OAuth clients can obtain tokens from Automation 360 server using standard OAuth 2.0 and OIDC flows, and use those tokens to securely access Automation 360 resources.
- Authorization Code
- Authorization Code with PKCE
- Refresh Token
Automation 360 server issues OAuth tokens with the following attributes:
- Token format - It indicates whether issued tokens are JSON Web Tokens (JWT).
- Access token expiration time - It indicates how long an access token remains valid before it expires.
- Refresh token lifetime - It indicates how long a refresh token can be used to obtain new access tokens.
- JWKS endpoint - It is the endpoint that exposes JSON Web Key Set (JWKS), containing the public keys used to verify JWT signatures.
These settings determine how long issued tokens remain valid and how external systems can validate or revoke tokens when integrating with Automation 360.
Registration methods
OAuth clients can be registered in two ways.
- Manually: An authorized user registers the client directly in the Control Room. See Register OAuth clients manually.
- Programmatically: An authorized user registers using OAuth Dynamic Client Registration (DCR), without requiring manual input in the Control Room. See OAuth Dynamic Client Registration.
Regardless of the registration method, all registered clients are visible and manageable on the page in the Control Room.