ACME Token Identifier and Challenges
draft-barnes-acme-token-challenge-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mary Barnes | ||
| Last updated | 2018-09-06 (Latest revision 2018-03-05) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
This document specifies an identifier and challenge type required to enable the Automated Certificate Management Environment (ACME) to issue certificates using a token for the challenge response. This token is issued by a administrative authority with whom the Certification Authority (CA) has a trust relationship. The entity requesting a certificate also has a relationship with the administrative authority, such that the administrative authority assigns a unique code to the entity. This entity code is included as part of the token that the administrative authority issues.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)