Protecting a web application with PingAccess in a gateway deployment - PingAccess - 6.2

Prerequisites

Before configuring your PingAccess deployment to protect a web application:

• PingAccess must be installed and running. See Installing and Uninstalling PingAccess for the full procedure.
• You must have a configured token provider. The procedures vary depending on the token provider. For more information, see:
  • PingFederate.
  • PingOne.
  • Common token provider.

Steps

After you have completed the following steps, your web application is protected.

1. Configuring a virtual host – A virtual host represents the external face of the site you will protect.
2. Configuring a site – A site contains the internal details of the site you will protect, including its actual location.
3. Configuring a web session – A web session defines the details of how user credential information is retained. This lets the token provider authenticate the user when it is required for a protected application.
4. Configuring a rule – Rules control who can access what content under what circumstances.
5. Configuring an identity mapping – An identity mapping lets you share identity information with the protected application as headers.
6. Configuring an application – An application joins the other pieces together, giving users access to the site according to the configured rules.