Web Access Management Agent deployment table

The following table describes the important configuration options for a Web Access Management (WAM) agent deployment. You can find specific use case information in Deploying for Agent Web Access Management.

To deploy a PingAccess agent, complete the steps in one of the following topics, depending on your web server:

The rest of PingAccess deployment is similar to WAM Gateway Deployment.

Configuration steps

Step	Description
Configure the connection to PingFederate.	PingAccess uses PingFederate to manage web session and authentication.
Configure the OpenID Connect Relying Party Client for PingAccess.	You must register the client with PingFederate and the client credentials configured in PingAccess to identify PingAccess when requesting authentication for users trying to access web applications.
Configure Web session details to enable protection of Web Resources.	Configure settings for secure web sessions such as timeout values, cookie parameters, and cryptographic algorithms.
Generate or Import Key Pairs and configure HTTP Listeners.	Defines the certificates and keys used to secure access to the PingAccess admin console and secure incoming HTTPS requests at runtime.
Set up your cluster for high availability.	Configure a cluster to facilitate high availability of critical services and increase performance and overall system throughput.
Add trusted CA certificates.	Define trust to certificates presented during outbound secure HTTPS connections.
Create a trusted certificate group.	Provide a trusted set of anchor certificates for authenticating outbound secure HTTPS connections.
Define virtual servers for protected resources.	Allow one server to share PingAccess resources without requiring all sites on the server to use the same host name. You can assign specific key pairs to virtual hosts.

Step

Description

Configure the connection to PingFederate.

PingAccess uses PingFederate to manage web session and authentication.

Configure the OpenID Connect Relying Party Client for PingAccess.

You must register the client with PingFederate and the client credentials configured in PingAccess to identify PingAccess when requesting authentication for users trying to access web applications.

Configure Web session details to enable protection of Web Resources.

Configure settings for secure web sessions such as timeout values, cookie parameters, and cryptographic algorithms.

Generate or Import Key Pairs and configure HTTP Listeners.

Defines the certificates and keys used to secure access to the PingAccess admin console and secure incoming HTTPS requests at runtime.

Set up your cluster for high availability.

Configure a cluster to facilitate high availability of critical services and increase performance and overall system throughput.

Add trusted CA certificates.

Define trust to certificates presented during outbound secure HTTPS connections.

Create a trusted certificate group.

Provide a trusted set of anchor certificates for authenticating outbound secure HTTPS connections.

Define virtual servers for protected resources.

Allow one server to share PingAccess resources without requiring all sites on the server to use the same host name.

You can assign specific key pairs to virtual hosts.