Qodex.ai

Configure a Non-Interactive Worker Application

Number of APIs: 3

This activity shows you how to create non-interactive worker application, configure its connection settings, get the application secret, and configure a token request.

Note: Worker applications are administrator applications that interact with the PingOne platform APIs. This application type supports only the OPENID_CONNECT protocol, and for non-interactive worker applications, no authorize request is needed to initiate a token request. For more information about worker applications, see Worker applications.

The following operations are supported by the PingOne APIs:

  • Create an application
  • Get the application secret
  • Initiate a token request

Best practices for application secrets

  • Do not store an application secret in applications that are publicly available.

  • For security purposes, regenerate application secrets regularly (see Update the application secret).

  • If you suspect an application secret has been compromised, generate a new application secret immediately.

Prerequisites

Get an access token from the worker application that you created in Getting Started with the PingOne APIs. To get a token from a different worker application in an alternate sandbox environment, run the token request endpoint using the client ID and client secret of your chosen worker app to authenticate the request. For more information, see GET a Worker Application Access Token.

Workflow order of operations

To configure a non-interactive worker application and initiate a token request, the following tasks must be completed successfully:

  1. Make a POST request to /environments/{{envID}}/applications to add a new application to the specified environment.

  2. Make a GET request to /environments/{{envID}}/applications/{{applicationID}}/secret to return the application secret.

  3. Make a POST request to /{{envID}}/as/token to get an access token.

  1. Step 1: Create a worker application POST {{apiPath}}/environments/{{envID}}/applications

  2. Step 3: Get a token POST {{authPath}}/{{envID}}/as/token

  3. Step 2: Get the application secret GET {{apiPath}}/environments/{{envID}}/applications/{{useCaseWorkerAppID}}/secret