Skip to main content

Automatic Certificate Management Environment (ACME) with OpenID Federation 1.0
draft-demarco-acme-openid-federation-01

Document Type Replaced Internet-Draft (candidate for acme WG)
Expired & archived
Authors Giuseppe De Marco , Brandon Pitman
Last updated 2025-11-26 (Latest revision 2025-10-20)
Replaced by draft-ietf-acme-openid-federation
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-acme-openid-federation
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

The Automatic Certificate Management Environment (ACME) protocol allows server operators to obtain TLS certificates for their websites, based on a demonstration of control over the website's domain via a fully-automated challenge/response protocol. OpenID Federation 1.0 defines how to build a trust infrastructure using a trusted third-party model. It uses a trust evaluation mechanism to attest to the possession of private keys, protocol specific metadata and miscellaneous administrative and technical information related to a specific entity. This document defines how X.509 certificates associated with a given OpenID Federation Entity can be issued by an X.509 Certification Authority through the ACME protocol to the organizations which are part of a federation built on top of OpenID Federation 1.0.

Authors

Giuseppe De Marco
Brandon Pitman

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)