acmev02 0.1.0

ACME client library to issue, renew and revoke TLS certificates.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69

use std::{
    collections::HashMap,
};
use serde::{self, Serialize, Deserialize};
use serde_json::Value;

/// ACMEv02 account information.
/// This holds the information described in [RFC 8555 §7.1.2](https://tools.ietf.org/html/rfc8555#section-7.1.2).
#[derive(Debug, Serialize, Deserialize)]
pub struct AcmeAccount {
    /// The status of this account.  Possible values are `"valid"`, `"deactivated"`, and `"revoked"`.  The value
    /// `"deactivated"` should be used to indicate client-initiated deactivation whereas `"revoked"` should be used to
    /// indicate server-initiated deactivation.
    pub status: String,

    /// An optional array of URLs that the server can use to contact the client for issues related to this account.
    /// Let's Encrypt only supports `mailto:` URLs at this time.
    pub contact: Option<Vec<String>>,

    /// Including this field in a `newAccount` request with a value of `true` indicates the client's agreement with the
    /// terms of service.  This field cannot be updated by the client.
    #[serde(rename="termsOfServiceAgreed")]
    pub terms_of_service_agreed: Option<bool>,

    /// Including this field in a `newAccount` request indicates approval by the holder of an existing non-ACME account
    /// to bind that account to this ACME account.  This field cannot be updated by the client.
    /// 
    /// This is not used by Let's Encrypt.
    #[serde(rename="externalAccountBinding")]
    pub external_account_binding: Option<Value>,

    /// A URL from which a list of orders submitted by this account can be fetched via a POST-as-GET request, as
    /// described in [RFC 8555 §7.1.2.1](https://tools.ietf.org/html/rfc8555#section-7.1.2.1).
    /// 
    /// This is required, but not implemented by Let's Encrypt
    /// ([Issue 3335](https://github.com/letsencrypt/boulder/issues/3335)).
    pub orders: Option<String>,

    /// Additional fields present that are not definied by RFC 8555.
    #[serde(flatten)]
    pub additional_fields: HashMap<String, Value>,
}

/// ACMEv02 account creation/lookup request.
/// This is the input structure to the newAccount request described in
/// [RFC 8555 §7.3](https://tools.ietf.org/html/rfc8555#section-7.1.2).
#[derive(Debug, Serialize, Deserialize)]
pub struct AcmeAccountRequest {
    /// An optional array of URLs that the server can use to contact the client for issues related to this account.
    /// Let's Encrypt only supports `mailto:` URLs at this time.
    pub contact: Option<Vec<String>>,

    /// Including this field in a `newAccount` request with a value of `true` indicates the client's agreement with the
    /// terms of service.
    #[serde(rename="termsOfServiceAgreed")]
    pub terms_of_service_agreed: Option<bool>,

    /// If this field is present with the value `true`, the server does not create a new account if one does not
    /// already exist.  This allows a client to look up an account URL based on an account key.
    #[serde(rename="onlyReturnExisting")]
    pub only_return_existing: Option<bool>,

    /// Including this field in a `newAccount` request indicates approval by the holder of an existing non-ACME account
    /// to bind that account to this ACME account.  This field cannot be updated by the client.
    /// 
    /// This is not used by Let's Encrypt.
    #[serde(rename="externalAccountBinding")]
    pub external_account_binding: Option<Value>,
}