API Access Management Gateway deployment table

The following table describes the important configuration options for deploying an API Gateway. You can find specific use case information in Deploying for Gateway API Access Management.

Configuration steps

Step	Description
Configure the connection to the PingFederate OAuth Authorization Server.	PingAccess uses this connection and credentials to validate incoming access tokens for securing application programming interface (API) calls.
Configure the OpenID Connect Relying Party Client for PingAccess.	You must register the client with PingFederate and the client credentials configured in PingAccess to authenticate PingAccess when validating incoming access tokens.
Generate or Import Key Pairs and configure HTTP Listeners.	Define 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.	Defines trust to certificates presented during outbound secure HTTPS connections.
Create a trusted certificate group.	Provides a trusted set of anchor certificates for use when authenticating outbound secure HTTPS connections.
Define virtual servers for protected applications.	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 the PingFederate OAuth Authorization Server.

PingAccess uses this connection and credentials to validate incoming access tokens for securing application programming interface (API) calls.

Configure the OpenID Connect Relying Party Client for PingAccess.

You must register the client with PingFederate and the client credentials configured in PingAccess to authenticate PingAccess when validating incoming access tokens.

Generate or Import Key Pairs and configure HTTP Listeners.

Define 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.

Defines trust to certificates presented during outbound secure HTTPS connections.

Create a trusted certificate group.

Provides a trusted set of anchor certificates for use when authenticating outbound secure HTTPS connections.

Define virtual servers for protected applications.

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.