Visual RFC.
ALL RFCs / RFC 8555
Read the RFC ↗
RFC 8555 / MECHANISMS

CSR, certificate, and revocation

05

Identifier authorization and possession of the certificate key are different checks.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 7.4 ↗
RFC 8555 · § 7.4EXAMPLE
3 / 3
CSR, certificate, and revocationIdentifier authorization and possession of the certificate key are different checks. Current state: Revoke separately.CSR, certificate, and revocationCSRidentifierscertificate public keyfinalizecertificateissued chainrevocation requestThe account key and certificate key have separate roles.
03
Revoke separately

An authorized signed revocation request can invalidate the certificate.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Finalize an order with a CSR containing the requested identifiers.

  • Finalize an order with a CSR containing the requested identifiers.
  • The CSR must have a valid signature; its key need not be the account key.
  • ACME defines a separate revocation endpoint.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. An order is a state machine
  2. One nonce for one signed request
  3. HTTP proves control of a path
  4. DNS proves control of a record
  5. CSR, certificate, and revocation

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗