Expand description
Configuration surface for the account zone (epic #1158, ticket #1162 / A3).
This is the deployment-facing knob. The [account] section names the
delegated zone apex, the zone-scoped DNS-01 credential, the ACME directory
to obtain the wildcard certificate from, and the wildcard address targets.
§Sane-degrade, not synthesized default
A deployment that configures no account zone must degrade sanely:
account minting is disabled with a clear error. AccountZoneConfig
therefore has no Default zone value — Default leaves zone = None,
and AccountZoneConfig::resolve_zone returns
AccountZoneError::Unset in that state. We must never synthesize a zone
name: a default would silently mint permanent DIDs under a domain the
operator never chose (epic one-way door #1).
§TOML
[account]
zone = "acct.example.com"
# Zone-scoped credential: the deployment's DNS provider accepts this and
# only this when writing records under the apex. Format is opaque to
# hyprstream — the product-layer DnsProvider interprets it.
dns01_credential = "ref:secretstore/account-zone-token"
acme_directory = "https://acme-v02.api.letsencrypt.org/directory"
acme_contact = "mailto:ops@example.com"
wildcard_ipv4 = "203.0.113.10"
wildcard_ipv6 = "2001:db8::20"Structs§
- Account
Http Config - Deployment configuration for the separate public hosted-account listener.
- Account
Zone Config - The
[account]configuration section.