Crate yacme_protocol

ACME JWT implementation and ACME request types.

Most ACME requests are authenticated as a JWT, signed by the account key. This module provides the implementation of that protocol, and the deserialization of the corresponding responses, as well as providing a Client type which can be used to track the correct Nonce through a series of requests.

Re-exports

• pub use client::Client;
• pub use errors::AcmeError;
• pub use request::Request;
• pub use response::Response;

Modules

• client
  Client for sending HTTP requests to an ACME server
• errors
  Errors which occur when working with an ACME Protocol
• fmt
  Utilities for formatting ACME request and response data in a human readable style, similar to that used in RFC8885
• jose
  JSON Object Signing and Encryption primitives used in RFC 8885 to implement the ACME protocol.
• request
  HTTP requests which adhere to RFC 8885
• response
  HTTP responses which adhere to RFC 8885

Structs

• Base64Data
  Wrapper type to indicate that the inner type should be serialized as bytes with a Base64 URL-safe encoding.
• Base64JSON
  Wrapper type to indicate that the inner type should be serialized as JSON and then Base64 URL-safe encoded and serialized as a string.
• Url
  Universal Resource Locator which provides a std::fmt::Debug implementation which prints the full URL (rather than the parsed parts) for compactness.

Type Definitions

• Result
  A result type which uses AcmeError as the error type.