An administrator is integrating a new PingAccess Proxied Application. The application will temporarily need a self-signed certificate during the…

In PingAccess, the Key Pairs section is used to manage the server's own private keys and their corresponding public certificates, which are essential for SSL/TLS termination. The scenario requires a new, self-signed certificate for a temporary Proof of Concept (POC). The most direct and initial action within the PingAccess administrative console to fulfill this requirement is to navigate to the Key Pairs section and use the built-in functionality to generate a new key pair along with a self-signed certificate. This action creates the necessary cryptographic materials directly within PingAccess without involving any external Certificate Authority (CA).

A. The Certificates section is for managing trusted certificates, such as those from CAs or backend web servers, not for creating the primary SSL server certificate and private key for PingAccess itself.

B. This is incorrect because the requirement is specifically for a self-signed certificate, not one issued by an internal Certificate Authority. Importing implies the certificate already exists elsewhere.

C. This is incorrect as the requirement is for a self-signed certificate suitable for a POC, not a certificate from a publicly trusted Certificate Authority, which is typically used for production.

1. Ping Identity Documentation, PingAccess Administrator's Guide, "Key pairs" section: This section explicitly states, "Key pairs are used by PingAccess to secure connections from clients... You can generate a new key pair and a self-signed X.509 certificate, generate a certificate signing request (CSR) for a new key pair, or import an existing key pair." This directly supports the action of creating a new self-signed certificate within the Key Pairs section.

Source: PingAccess 7.3 Administrator's Guide, Section: "Key pairs".

2. Ping Identity Documentation, PingAccess Administrator's Guide, "Trusted certificates" section: This documentation clarifies the purpose of the "Certificates" section, stating, "The Trusted Certificates page lists certificates that PingAccess trusts when it acts as a client." This confirms that option A is incorrect as this area is for managing trust, not for creating the server's own identity certificate for SSL termination.

Source: PingAccess 7.3 Administrator's Guide, Section: "Trusted certificates".