Register OAuth clients manually - Authorized users can manually register OAuth clients in the Automation 360 Control Room .

Automation 360

Authorized users can manually register OAuth clients in the Automation 360 Control Room.

Note: To register OAuth clients programmatically, see OAuth Dynamic Client Registration.

Before you begin

Ensure that your user role includes one of the following Control Room permissions:
  • Application Registration View – to view existing OAuth clients.
  • Application Registration Manage – to create, update, and delete OAuth clients.

Procedure

  1. Log in to Automation 360 Control Room.
  2. From the left navigation, select Manage.
  3. Navigate to OAuth clients. It lists all existing OAuth clients registered in the Control Room, if any.View OAuth client details
  4. Click Create client to register a new OAuth client.
    Create new OAuth clients
  5. Enter a unique Application name to identify the OAuth client.
  6. Select an Application type from the drop-down list.
    • Regular Web - Use this Application type when you intend to use a client secret. It is typically used when your client resides on a secure web server that can protect the secret.
    • Single Page Application - Use this Application type when you intend to use PKCE and forego passing a client secret. It is typically used when your client resides in an unprotected environment that cannot ensure the protection of the secret.
  7. Optional: Enter a Description for the OAuth client.
  8. Enter one or more Redirect URIs to validate the client and click Add. Separate each redirect URI with a comma. Currently, you can add up to 10 redirect URIs.
    Note: When you save the OAuth client configuration, the system checks that all Redirect URIs use HTTPS. Once they are validated, client metadata is generated.
  9. Click Create client.

    The newly created client will be shown on the Manage > OAuth clients page. Click on the created Application name to view the OAuth client details, consisting of automatically generated client metadata. See View and manage OAuth clients.

    OAuth clients listed in this page

    All generated values can be copied individually. Share the Client ID, Client secret, and endpoint URLs with the external application owner so they can configure them in their OAuth client application.

    Note:
    • Treat the Client secret like a password. It must only be shared with trusted administrators of the external application and stored in a secure location, such as a secret manager.
    • Authorized users can view the Client secret from the OAuth clients page at any time.

    Auditing

    Control Room records an audit event when an OAuth client is created manually. See OAuth client audit entries.

    These audit records support governance, compliance, and troubleshooting for administrators managing OAuth client registrations.