Struct ChallengeRegistry 

pub struct ChallengeRegistry { /* private fields */ }

The configured validators plus the settings the handlers need to apply them.

Cheap to clone behind the Arc it is always held in.

Implementations

impl ChallengeRegistry

pub fn new( validators: Vec<Arc<dyn ChallengeValidator>>, enabled: Vec<String>, bypass: bool, timeout: Duration, ) -> Self

Builds a registry directly from parts. Mostly useful to tests; production goes through from_config.

pub fn enabled_types(&self) -> &[String]

The challenge types offered, in the order they were configured.

pub fn is_bypassed(&self) -> bool

Whether triggering a challenge skips validation entirely.

pub fn types_for(&self, wildcard: bool) -> Vec<&str>

The challenge types to create on a new authorization.

A wildcard can only be proved by dns-01 (RFC 8555 §8.4): control of one host says nothing about the rest of the zone. The other types are therefore filtered out for a wildcard authorization — possibly leaving nothing, which the caller turns into a rejectedIdentifier rather than creating an authorization no client could ever satisfy.

pub async fn validate( &self, typ: &str, ctx: &ValidationContext<'_>, ) -> Result<(), ChallengeError>

Runs the validator for typ within the configured budget.

Trait Implementations

impl Debug for ChallengeRegistry

fn fmt(&self, formatter: &mut Formatter<'_>) -> Result

dyn ChallengeValidator is not Debug, and enabled says everything the validator list would.

impl Default for ChallengeRegistry

fn default() -> Self

Bypassing, offering http-01 alone.

This is a test default and deliberately no longer matches from_config(&ChallengeConfig::default()), which validates for real. The server never reaches this impl — Profile::build_all always goes through from_config — and a test suite that has no http-01 responder on port 80 needs a registry that answers without one. The divergence is pinned by the_test_default_bypasses_where_the_configured_default_does_not so it stays a decision rather than a drift.