1. Go to Connections > Applications.
  2. Browse or search for the application that you want to edit.
  3. Click the application entry to open the details panel. Click the tab that you want to edit, and then click the pencil icon.
  4. For Overview, enter or edit the following:
    • Application Name: A unique identifier for the application.
    • Description (optional): A brief characterization of the application.
    • Icon (optional). A pictorial representation of the application. Use a file up to 1MB in JPG, JPEG, GIF, or PNG format.
    • Home page URL: The default home page for the application.
    • Signon URL: The URL to which the application requests that the end user be redirected to sign on.
  5. For Configuration, enter or edit the following:
    Field Description

    Response type

    Select code, token, or ID token for the response type. See Response types.

    Grant type

    Select authorization code, implicit, refresh token, or client credentials for the grant type. See Grant types.

    PKCE enforcement

    Select a value for PKCE code challenge enforcement. This value determines how the application creates the code challenge from the code verifier. See PKCE enforcement.


    PKCE enforcement is available for Authorization Code grant type applications only.

    Redirect URIs

    The address to which PingOne forwards the OIDC response after authentication. The Redirect URI cannot contain a fragment component, such as #somedata. For more information, see Redirection endpoint in the IETF documentation.


    You can use wildcards for flexibility in managing redirect URIs. See Redirect URIs.

    Signoff URLs

    The URL to which the application requests that the browser be redirected using the post_logout_redirect_uri parameter after a logout has been performed.

    Token Endpoint Authentication Method

    Select none, client secret basic, or client secret post for the token endpoint authentication method.

  6. For Resources, select the OAuth scopes for the application by selecting the check box for the appropriate scopes. Click the Selected scopes tab to see the scopes that are currently selected for the application.

    The OAuth scopes determine the resources that the application can access. If you add OIDC scopes here, the application inherits the attributes associated with that scope.

  7. For Policies, select the authentication policies for the application.

    If you have a DaVinci license, you can select PingOne policies or DaVinci Flow policies, but not both. If you don’t have a DaVinci license, you’ll see PingOne policies only.

    To use a PingOne policy, Click + Add policies and then select the policies that you want to apply to the application. Click Add. The policies are applied in the order in which they appear in the list. PingOne evaluates the first policy in the list first. If the requirements of the policy are not met, PingOne moves to the next policy in the list. For more information, see Authentication policies for applications.

    To use a DaVinci Flow policy, you must clear all PingOne policies. Click the Deselect all PingOne policies button. In the confirmation message, click Continue. Click the DaVinci Policies tab, and then select the policies that you want to apply to the application. PingOne applies the first policy in the list. For OAuth-based applications, you can specify another policy in the acr_values parameter in the authorization request.

  8. For Attribute mappings, select a PingOne user attribute and map it to an attribute in the application you are adding. For more information, see Mapping attributes.
    • Enter an application attribute and then select the corresponding PingOne attribute from the list.
    • Click the gears icon to use the expression builder to build an attribute mapping. See Using the expression builder.
  9. For Access, enter or edit the following:
    • Admin only access: Specifies that a user with an administrator role is required to access the application. The user must have one of the following roles: Organization Admin, Environment Admin, Identity Data Admin, or Client Application Developer.
    • Group membership policy:. Select the group membership policy for the application. For more information, see Groups.
  10. For Roles, select the roles for the worker application.

    By default, a worker application has the same roles as the user that created the application. For more information, see Configuring roles for a worker application.

  11. Click Save.