Managing certificates for key pairs with ACME - PingAccess - 7.0

PingAccess

bundle
pingaccess-70
ft:publication_title
PingAccess
Product_Version_ce
PingAccess 7.0
category
Product
pa-70
pingaccess
ContentType_ce

Manage key pairs using the automatic certificate management environment (ACME) protocol, which automatically obtains and renews certificates indirectly signed by a well-known trust anchor.

The ACME protocol is an Internet Engineering Task Force (IETF) proposed standard protocol that automates the signing of TLS certificates by a certificate authority (CA).

The ACME certificate management option in PingAccess uses the staging Let’s Encrypt ACME CA by default.

Note:

The Let's Encrypt staging server that PingAccess uses by default has more lenient rate limits, but it doesn't generate functional certificates, to support its use for testing purposes. For more information about rate limits, see the Let's Encrypt documentation.

After testing your environment, you must switch to a production server using the PingAccess Administrative API.

  1. Use a GET call to /pa-admin-api/v3/acme/servers to retrieve the ID of a production server.
  2. Use a PUT call to /pa-admin-api/v3/acme/servers/default to set the production Let's Encrypt server as the default.

To add more ACME servers, use a POST call to /pa-admin-api/v3/acme/servers. See the Administrative API endpoints documentation for more information about the administrative API endpoints.

  1. Click Security and then go to Key Pairs.
  2. Click the Pencil icon, and then click Manage with ACME for the key pair.
    The ACME status changes to Pending. When the protocol has completed, the status changes to Valid if the protocol completed successfully.