This table describes the important configuration options for a Web Access Management (WAM) agent deployment.
For specific use case information, see Deploying for Agent Web Access Management.
Deploy PingAccess agent using the following steps:
- Install PingAccess agent on web server. For more information, see instructions in PingAccess Agent for Apache Installation or PingAccess Agent for IIS Installation, depending on your specific web server.
- Define the agents and download agent bootstrap.properties file using the download field in the Shared Secrets field.
- Deploy the agent bootstrap.properties file to agents. For more information, see PingAccess Agent Configuration .
The rest of PingAccess deployment is similar to Web Access Management Gateway Deployment.
PingAccess uses PingFederate to manage web session and authentication.
The client must be registered with PingFederate and the client credentials configured in PingAccess to identify PingAccess when requesting authentication for users trying to access web applications.
Configures settings for secure web sessions such as timeout values, cookie parameters, and cryptographic algorithms.
Defines the certificates and keys used to secure access to the PingAccess administrative console and secure incoming HTTPS requests at runtime.
Facilitates high availability of critical services, and increases performance and overall system throughput.
Defines trust to certificates presented during outbound secure HTTPS connections.
Provides a trusted set of anchor certificates for use when authenticating outbound secure HTTPS connections.
Allows one server to share PingAccess resources without requiring all sites on the server to use the same host name. If SNI is available (Java 8), specific key pairs can be assigned to virtual hosts.