Application field descriptions
The following table describes the fields available for managing applications on the Applications tab.
Field | Required | Description | ||||
---|---|---|---|---|---|---|
Name |
Yes |
A unique name for the application. |
||||
Description |
No |
An optional description for the application. |
||||
Context Root |
Yes |
The context at which the application is accessed at the site.
|
||||
Case Sensitive Path |
No |
Indicates whether or not to make request Uniform Resource Locator (URL) path matching case sensitive. |
||||
Virtual host(s) |
Yes |
Specifies the virtual host for the application. Click Create to create a virtual host. See Creating new virtual hosts for more information. |
||||
Application Type |
Yes |
Specifies the application type, either
Select an Authentication Challenge Policy to produce authentication challenges for the application. You can enter an OpenID Connect Provider Issuer URL to replace the visible URL during authentication if the token provider supports it. Select a Risk Policy to enforce continuous authorization with PingOne Protect on the application.
Click +Create underneath the desired field to create a new web session, identity mapping, authentication challenge policy, or risk policy.
* If the Application Type is If you want to configure different DPoP settings for the application than the global settings you specified in the token provider, follow step 9 in Adding application resources to complete your configuration. Click Create to create an access validation or identity mapping.
Select an Authentication Challenge Policy to produce authentication challenges for the application. In this configuration, the web session is required and the API is protected by default. Click Create to create an access validation, web session, web identity mapping, API identity mapping, or authentication challenge policy. You can enter an OpenID Connect Provider Issuer URL to replace the visible URL during authentication if the token provider supports it. Specify whether you want to enable SPA Support. If you want to configure different DPoP settings for the application than the global settings you specified in the token provider, follow step 9 in Adding application resources to complete your configuration. |
||||
Destination |
Yes |
Specifies the application destination type, either
|
||||
Enabled |
No |
Select to enable the application and allow it to process requests. |
Advanced Settings
To configure advanced settings on an application, expand the Show Advanced Settings section at the bottom of the Applications tab, just above the Enabled check box. These settings are optional.
Field | Description | ||
---|---|---|---|
Use context root as reserved resource base path |
Selecting the Use context root as reserved resource base path check box provides access to reserved PingAccess resources and runtime API endpoints from the context root of this application in addition to the globally-defined reserved application context root.
When this setting is enabled, PingAccess adds this application’s context root before the reserved application context root in any content that references the reserved path to ensure that it responds to those requests. For example, the path to an endpoint changes from If you have a web application with a context root of |