---
title: Managing certificates for key pairs with ACME
description: 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).
component: pingaccess
version: 8.2
page_id: pingaccess:pingaccess_user_interface_reference_guide:pa_managing_certificates_for_key_pairs_with_acme
canonical_url: https://docs.pingidentity.com/pingaccess/9.1/pingaccess_user_interface_reference_guide/pa_managing_certificates_for_key_pairs_with_acme.html
llms_txt: https://docs.pingidentity.com/pingaccess/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: March 27, 2024
superseded_by: https://docs.pingidentity.com/pingaccess/9.1/pingaccess_user_interface_reference_guide/pa_managing_certificates_for_key_pairs_with_acme.html
section_ids:
  about-this-task: About this task
  steps: Steps
  result: Result:
---

# Managing certificates for key pairs with ACME

## About this task

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) *(tooltip: \<div class="paragraph">
\<p>An entity that issues digital certificates.\</p>
\</div>)*.

By default, the ACME certificate management option in PingAccess uses the staging [Let's Encrypt](https://letsencrypt.org/) ACME CA.

|   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | The Let's Encrypt staging server, which 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](https://letsencrypt.org/docs/rate-limits/).After testing your environment, you must switch to a production server using the PingAccess administrative application programming interface (API) *(tooltip: \<div class="paragraph">&#xA;\<p>A specification of interactions available for building software to access an application or service.\</p>&#xA;\</div>)*.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`. For more information about the administrative API endpoints, see [Administrative API endpoints](../reference_guides/pa_admin_api_endpoints.html). |

To manage certificates with ACME:

## Steps

1. Click **Security**, then go to **Key Pairs > Key Pairs**.

2. Click the **Pencil** icon, and then click **Manage with ACME** for the key pair.

   ### Result:

   The ACME status changes to **Pending**. When the protocol has completed, the status changes to **Valid** if the protocol completed successfully.
