Struct Profile 

pub struct Profile {
    pub name: String,
    pub path: String,
    pub base_url: String,
    pub signer_info: Arc<dyn SignerInfo>,
    pub filter: Arc<FilterPolicy>,
    pub challenges: Arc<ChallengeRegistry>,
    pub order: OrderConfig,
    pub eab: EabConfig,
    pub meta: MetaConfig,
    pub notify: Arc<NotifyDispatcher>,
}

One ACME endpoint: its identity, its URLs, and the three subsystems that answer for it.

Everything per-endpoint lives here rather than beside the global config in AppState, so a handler cannot pair one profile’s signer with another’s base URL — the two always travel together.

Fields

name: String

The configured name ([profiles.<name>]), also the URL segment and the value stored in accounts.profile / orders.profile.

path: String

Where the router mounts it: /profile/<name>.

base_url: String

The public base for every URL this endpoint hands out and for the RFC 8555 §6.4 url check: server.base_url + Profile::path.

signer_info: Arc<dyn SignerInfo>

What this endpoint’s signer publishes — its CRL, anchor, renewal opinion and http-01 tokens — and where its revocations go. Built from public material, so every role has one.

There is deliberately no backend here. Signing and revoking need the key, which only the worker role holds, and only the job handlers it runs are handed one (GenerationParts::signers). A profile is what a request is served from, so leaving the backend off it is what makes “a request never signs” a type error rather than a convention.

filter: Arc<FilterPolicy>

challenges: Arc<ChallengeRegistry>

order: OrderConfig

eab: EabConfig

meta: MetaConfig

The optional meta members this endpoint’s directory advertises (RFC 8555 §7.1.1). Per-profile, like everything else here: two endpoints on one process can have different terms of service.

notify: Arc<NotifyDispatcher>

Implementations

impl Profile

pub fn new(name: &str, base_url: &str, parts: ProfileParts) -> Self

Assembles a profile, deriving its path and base URL from its name — the two are never configured, so they cannot drift from each other or from what the database records.

pub fn directory_url(&self) -> String

This endpoint’s directory URL — where a client starts.

Derived here rather than format!-ed at each of the three call sites (the startup log line, the admin API’s profile listing, and anything added later), all of which have to agree with what build_router actually mounts.