Page created: 23 Jun 2020
|
Page updated: 24 Jul 2020
You can promote all PingAccess applications assigned to you.
The information required to promote PingAccess Web applications, API applications, and Web + API applications varies by type. Prepare to provide the following information:
- Virtual hosts: Virtual hosts enable PingAccess to protect multiple
application domains and hosts. A virtual host is defined by the host name
and host port, and is required to promote Web, API, and Web + API
applications.
See Virtual hosts in the PingAccess guide for details.
- Web session: Web sessions define the policy for web application
session creation, lifetime, timeouts, and their scope, and are required for
Web + API applications. However, they are optional in Web
applications.
See Web Sessions in the PingAccess guide for details.
- Identity mappings: Identity mappings make user attributes available
to back-end sites that use them for authentication. There are many types of
identity mappings, each with different behavior and a distinct set of fields
to specify the identity mapping behavior. You can add Web and API identity
mappings when promoting Web, API, and Web + API applications.
See Identity mappings in the PingAccess guide for details.
- Access validation method: API and Web + API applications can be
configured to use access token validators to locally verify signed or
encrypted access tokens.
See Token validation in the PingAccess guide for details.
- Agents: Agents are web server plugins that are
installed on the web server hosting the target application. They intercept
client requests to protected applications and allow or deny the request to
proceed.
See Agents in the PingAccess guide for details.
- Sites: Sites are the target applications, endpoints,
or APIs, which PingAccess Gateway is protecting, and to which authorized
client requests are forwarded.
See Sites in the PingAccess guide for details.