Enum DomainLinkageError 

#[non_exhaustive]
pub enum DomainLinkageError {
    InvalidOrigin(String),
    InvalidContext(String),
    TypPresent(String),
    UnexpectedHeaderParameter(String),
    UnexpectedClaim(String),
    MissingClaim(&'static str),
    IdPresent,
    MissingContext,
    MissingType,
    MissingExpirationDate,
    SubjectNotDid(Option<String>),
    SubjectMismatch {
        role: &'static str,
        found: String,
        subject: Did,
    },
    InvalidOriginProperty(Option<Value>),
    OriginMismatch {
        expected: String,
        found: String,
    },
    Validation(ValidationError),
    NoCredentialFor(Did),
    NoValidCredential(BTreeMap<usize, DomainLinkageError>),
    InvalidService {
        id: DidUrl,
        reason: String,
    },
    InsecureOrigin(String),
    Http {
        url: Url,
        source: HttpError,
    },
    NotPublished {
        url: Url,
        status: u16,
    },
    HttpStatus {
        url: Url,
        status: u16,
    },
    InvalidConfiguration {
        url: Url,
        source: Error,
    },
    Resolution(ResolutionError),
    TooManyOrigins(usize),
    TooManyCredentials(usize),
}

Available on crate feature domain-linkage only.

Why a domain linkage credential or configuration did not validate.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

InvalidOrigin(String)

An origin is not scheme://host[:port].

InvalidContext(String)

The configuration’s @context is not CONTEXT.

TypPresent(String)

The JWT header has a typ, which the format forbids.

UnexpectedHeaderParameter(String)

The JWT header has a parameter other than alg and kid.

UnexpectedClaim(String)

The JWT payload has a claim other than iss, sub, nbf, exp and vc.

MissingClaim(&'static str)

A required claim is missing: iss, sub, exp or nbf.

IdPresent

The credential has an id, which the format forbids.

MissingContext

The credential’s context does not include CONTEXT.

MissingType

The credential’s type does not include CREDENTIAL_TYPE.

MissingExpirationDate

The credential has no expirationDate.

SubjectNotDid(Option<String>)

credentialSubject.id is missing or not a DID.

SubjectMismatch

The issuer, iss or sub differs from credentialSubject.id.

Fields

role: &'static str

issuer, iss or sub.

found: String

The value found.

subject: Did

credentialSubject.id.

InvalidOriginProperty(Option<Value>)

credentialSubject.origin is missing or not one string.

OriginMismatch

credentialSubject.origin is not the origin the resource was fetched from.

Fields

expected: String

The normalized origin expected.

found: String

The credential’s origin, normalized.

Validation(ValidationError)

The credential did not decode or validate as a credential JWT.

NoCredentialFor(Did)

The configuration holds no JWT credential for the DID.

NoValidCredential(BTreeMap<usize, DomainLinkageError>)

No credential of the configuration validated; the error of each JWT entry by its position.

InvalidService

A LinkedDomains service does not list one or more origins.

Fields

id: DidUrl

The id of the service.

reason: String

What is wrong with it.

InsecureOrigin(String)

The origin is not https, the only scheme the resource is fetched over.

Http

The HttpClient got no response.

Fields

url: Url

The URL of the resource.

source: HttpError

Why there was no response.

NotPublished

The origin publishes no DID configuration: the server answered 404 or 410. A legitimate state of an origin rather than a failure; see is_not_published.

Fields

url: Url

The URL of the resource.

status: u16

404 or 410.

HttpStatus

The server answered with a status other than 2xx, 404 and 410.

Fields

url: Url

The URL of the resource.

status: u16

The status code.

InvalidConfiguration

The body is not a DID configuration resource: not JSON, not of its shape, or of another @context.

Fields

url: Url

The URL of the resource.

source: Error

Why the body did not deserialize.

Resolution(ResolutionError)

The DID did not resolve.

TooManyOrigins(usize)

The origin was not fetched: the DID document lists more origins than the client’s limit, given here.

TooManyCredentials(usize)

The entry was not validated: the configuration holds more JWT entries, or more naming the DID, than the validator’s limit, given here.

Implementations

impl DomainLinkageError

pub fn is_not_published(&self) -> bool

Whether the origin publishes no DID configuration (NotPublished), as opposed to a configuration that could not be fetched, read or validated.

Trait Implementations

impl Debug for DomainLinkageError

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

Formats the value using the given formatter.

impl Display for DomainLinkageError

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

Formats the value using the given formatter.

impl Error for DomainLinkageError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.

impl From<CredentialError> for DomainLinkageError

fn from(error: CredentialError) -> Self

Converts to this type from the input type.

impl From<ResolutionError> for DomainLinkageError

fn from(source: ResolutionError) -> Self

Converts to this type from the input type.

impl From<ValidationError> for DomainLinkageError

fn from(source: ValidationError) -> Self

Converts to this type from the input type.