Create an API client with DCR

You can create an API client that uses a dynamic client registration (DCR) provider for authentication. This enables API consumers to generate their own credentials in the Developer Portal instead of requiring manual provisioning by an API Platform Admin.

PREREQUISITES

Before you begin, ensure you have completed the following tasks:

Set up client details

Complete the following steps to set up the client details. These steps are the same for all authentication methods.

1
Add an API client
1

Go to Platform > API Platform.

2

Select the Clients tab.

3

Click + Add new client.

Add new clientAdd new client

2
Set up client details
1

Enter a Name for your client. Use a descriptive identifier, such as the client’s company or department name.

Set up client detailsSet up client details

2

Enter a Description for the client.

3

Upload a Client logo. Drag and drop a JPG/PNG image or click Upload from device to select a file. This logo visually identifies your client in the portal.

4

Enable the Grant client access to portal toggle to enable portal access. This grants your client permission to browse published API collections and manage their API keys. If your client only requires API tokens for testing or internal purposes, you can leave the toggle disabled.

5

Enter the Email address of the client. The system sends an invitation to this email, allowing your client to log in and access the portal.

6

Click Next to proceed to the Define access configuration screen, where you can configure your client’s API access.

Define access configuration

The access configuration step determines how the client authenticates with your APIs. Select an authentication method and configure the DCR-specific settings.

The following sections describe the DCR-enabled configuration for each supported authentication method:

OpenID Connect with DCR

Complete the following steps to configure an API client that uses OpenID Connect with a DCR provider.

1

Use the Authentication method drop-down menu to select OpenID Connect (DCR enabled).

Select authentication methodSelect authentication method

2

Use the API collections to include drop-down menu to select one or more API collections. This defines the APIs your client can access and invoke in the portal. You can also create a client without collections to allow discovery before you grant API access.

3

Optional. Assign a Policy to control your client's API usage. Policies define rules such as rate limits or usage quotas.

4

Click Next.

5

Use the Discovery method drop-down menu to select DCR provider.

The DCR provider option appears in the Discovery method drop-down menu only after you configure at least one DCR provider in Settings > Developer Portal > Dynamic client registration. The other Discovery URL and JSON Web key set (JWKS) URL options follow the existing OpenID Connect configuration flow. Refer to OpenID Connect authentication for more information.

6

Use the DCR provider drop-down menu to select the provider you plan to use for this client. The drop-down lists all DCR providers you configured that use the OpenID Connect authentication method.

Select DCR providerSelect DCR provider

7

Click Next to proceed to the Set up authentication step and complete the remaining configuration.

After you complete the configuration, Workato creates the API client. The client appears on the Clients page with its authentication method and DCR provider details.

OAuth 2.0 Token Introspection with DCR

Complete the following steps to configure an API client that uses OAuth Token Introspection 2.0 with a DCR provider.

1

Use the Authentication method drop-down menu to select OAuth 2.0 Token introspection (DCR enabled).

Select authentication methodSelect authentication method

2

Use the DCR provider drop-down menu to select the provider you plan to use for this client. The drop-down lists all DCR providers you configured that use the OAuth 2.0 Token Introspection authentication method.

Select No provider (Manual setup) to configure Token Introspection manually without a DCR provider. This requires you to configure the HTTP connection and introspection endpoint individually. Refer to OAuth 2.0 Token Introspection authentication for more information.

3

Use the API collections to include drop-down menu to select one or more API collections. This defines the APIs your client can access and invoke in the portal. You can also create a client without collections to allow discovery before you grant API access.

4

Optional. Assign a Policy to control your client's API usage. Policies define rules such as rate limits or usage quotas.

5

Click Next to create the client.

After you complete the configuration, Workato creates the API client. The client appears on the Clients page with its authentication method and DCR provider details.

Last updated: