Create a new OpenID Connect (OIDC) application, or modify an existing application in PingOne SSO for SaaS Apps.
Before you initially add an OICD application, you need to configure the access token your account will use for OIDC applications. These are account-level settings that will be inherited at the application level when you add or update and application, as you are doing here.
PingOne SSO for SaaS Apps returns OIDC user attributes in different ways depending on the response_type parameter.
The contents of the ID token depend on whether or not the application also returns an access token:
- For flows that return both an access token and an ID token (such as authorization
code flow, or implicit flows where the response_type includes
token) the ID token contains the
suband, if requested,
userinfoendpoint contains all of the attributes for the requested scopes and attributes configured on the User Info tab for the application, if the
openidscope was requested.
- For flows that don't return an access token, the ID token contains all of the
attributes for the requested scopes and any attributes configured on the
User Info tab for the application, if the
openidscope was requested. The
userinfoendpoint is inaccessible in this case because no access token is issued.
The access token contains attributes configured at.
When updating an application, any changes you make to the existing configuration parameters will be reflected in your customer's or partner's connection to the application.
However, if your customer or partner has changed the parameter settings in their PingOne for Enterpriseaccount, their local settings will override your updated configuration.
In other words, configuration updates made by a service provider at the application level will not override configuration updates made at the connection level.
- Go to .
Add a new application or edit an existing application.
- To create a new application, click Add Application. See Step 3 for new application types.
- To update an existing application, expand the application and click the Pencil icon. Skip to Step 4.
Select the type of application you want to add and click
To create an application that is accessed and used within a browser, click Web App.
To create an application that is stored locally and run on a desktop or device, click Native App.
To create an API-driven front-end application, such as applications using Node.js or Angular, click Single Page App.
If you want full control of all available configuration parameters, click Advanced Configuration.
- In the Application Name field, enter a name for the application.
In the Short Description field, enter a description of the
Customers will be able to see your description.
- In the Category list, select a category for the application.
Click Icon to add an icon for this application.
The icon file can be up to 1 Mb in size. The supported graphics formats are JPG, PNG and GIF.
- Click Next.
To enable or disable a custom valid duration for the application access token,
click the Override Access Token Lifetime toggle.
When this control is enabled, a Minutes selector is displayed. The valid range is 1 - 60 minutes. The default value is inherited from your account-level OAuth settings.
If you enabled the override, enter the number of minutes access token lifetime in
the Minutes field.
The valid range is 1 - 60 minutes. The default value is inherited from your account-level OAuth settings. For more information, see Configuring your OAuth settings.
Select the grant types allowed for the application.
Available grant types are determined by the application type. For more information, see OIDC application grant types.
If you selected Refresh Token, configure the token
- Click the Override Refresh Idle Lifetime toggle to override the global OAuth setting for the application.
- In the Refresh Token Idle Lifetime field, enter the number of minutes that a refresh token can be idle before being used again.
- Click the Override Refresh Token Max Lifetime toggle to override the global OAuth setting for this application.
- In the Refresh Token Max Lifetime field, enter the maximum number of minutes that a refresh token can be valid.
- Copy the Client ID, Discovery URL, and Issuer values to use later in integrating the application with PingOne SSO for SaaS Apps.
- Optional: For applications that use the Authorization Code grant type, you can click Add Secret to generate up to two client secrets to pair with the client ID.
- Click Next
In the Start SSO URL field, enter the URL to use for SSO to
This is the URL to which application users will redirect to initiate SSO to PingOne for Enterprise using OIDC.
In the Redirect URI field, enter URIs for PingOne SSO for SaaS Apps to send responses to for the application's
Tip: Click Add URL to define multiple redirect URIs.
- Optional: In the Logout URI field, enter the URI to which PingOne for Enterprise sends a user for single logout (SLO).
- Click Next
Click Add Attribute to configure attributes returned by the
UserInfoendpoint for this application when the
openidscope is included in the authorization request.
- In the Attribute Name field, enter a name for the attribute.
- Select the Required check box to require the attribute mapping when a UserInfo request is made for this application.
The sub (Subject) attribute is required for all UserInfo requests.
The idpid attribute is used by PingOne for Enterprise to identify the identity provider (IdP), and is included in the attribute contract by default.
- Click Next.
Click the + icon to add scopes to the allowed list, or click
the - icon to remove them.
These OAuth user scopes are the user resources to which the application will request access. The openid scope is expected to always be included in the authorization request.
- Click Save.