An administrator is integrating a new PingAccess Proxied Application. The application will use an SSL certificate issued by a publicly trusted…

For PingAccess to terminate SSL/TLS for a proxied application, it must possess the server's private key and its corresponding public certificate chain. In PingAccess, this combination of a private key and a certificate is managed as a "Key Pair". The standard and most common method for importing a private key along with its full certificate chain is by using a PKCS#12 (or PFX) file. This file format securely bundles all necessary components, which are then imported into the "Key Pairs" section of the PingAccess administrative console to be used by an HTTPS listener.

A. The "Certificates" section is for managing trust anchors (like CA certificates), not for storing the server's own private key and certificate used for SSL termination.

B. While a PKCS#12 file is the correct format, it must be imported into "Key Pairs," not "Certificates," as the latter is for trust stores and does not handle private keys.

C. The "Key Pairs" section is correct, but importing only the public key and certificate chain is insufficient. The private key is mandatory for SSL termination, which this option omits.

1. Ping Identity PingAccess 7.3 Administrator's Guide, Section: Managing key pairs.

Page/Section Reference: In the introduction to the "Managing key pairs" section, the documentation states, "Key pairs are used by PingAccess as server certificates for TLS connections...". It further details the import process: "You can import a key pair from a PKCS#12 file...". This confirms that the "Key Pairs" section is the correct location and PKCS#12 is a valid import format for this purpose.

2. Ping Identity PingAccess 7.3 Administrator's Guide, Section: Configuring HTTPS listeners.

Page/Section Reference: This section explains that when configuring an HTTPS listener, you must "Select the key pair that PingAccess presents to clients for the TLS handshake." This directly links the imported Key Pair to the function of SSL termination for an application.

3. Ping Identity PingAccess 7.3 Administrator's Guide, Section: Managing certificates.

Page/Section Reference: The documentation for this section clarifies its purpose: "Use this page to manage certificates for trusted certificate authorities (CAs)...". This confirms that the "Certificates" section is a trust store and is not the correct location for the server's own SSL certificate and private key.