A web application is a browser-based application with a server-side component, such as .NET web apps, JSP/Java, Node.js, or Ruby on Rails.
Web applications typically have functions similar to desktop applications. Web applications can use SAML or OIDC for authentication.
A web application includes the following configuration.
Create App Profile |
The application name and description. |
Configure |
The application's redirect URL. |
Grant Access |
To your application (for your customers to trigger authentication requests). |
Attribute Mapping |
Map your PingOne user-defined attributes to the corresponding application attributes, for accessibility between users and your app. |
Every user authentication event occurs in the context of a SAML or OIDC application. When you invoke MFA through an OIDC request, you'll need to provide a client ID, which is the ID of your web application.
A worker app is used to make backend calls. In contrast, a web app (or native app or SPA app) is required for invoking an authentication flow.
Creating a web application console
Creating a web application API alternative
Application developers can use the API operations to create a web application. Use the access token generated through the worker app.