pub struct AuthenticatorSelectionCriteria {
pub authenticator_attachment: Option<AuthenticatorAttachment>,
pub resident_key: Option<ResidentKeyRequirement>,
pub require_resident_key: bool,
pub user_verification: UserVerificationRequirement,
}Expand description
Relying Parties may use this type to specify their requirements regarding authenticator attributes.
https://w3c.github.io/webauthn/#dictdef-authenticatorselectioncriteria
Fields§
§authenticator_attachment: Option<AuthenticatorAttachment>If this member is present, eligible authenticators are filtered to be only those
authenticators attached with the specified AuthenticatorAttachment modality. If this
member is absent, then any attachment modality is acceptable. The value SHOULD be a member
of AuthenticatorAttachment but client platforms MUST ignore unknown values, treating an
unknown value (None) as if the member does not exist.
See also the PublicKeyCredential::authenticator_attachment member, which can tell what
authenticator attachment modality was used in a successful create() or get() operation.
resident_key: Option<ResidentKeyRequirement>Specifies the extent to which the Relying Party desires to create a client-side discoverable credential.
For historical reasons the naming retains the deprecated “resident” terminology.
The value SHOULD be a member of ResidentKeyRequirement but client platforms MUST ignore
unknown values, treating an unknown value (None) as if the member does not exist. If no
value is given then the effective value is required if Self::require_resident_key is true
or discouraged if it is false or absent.
See ResidentKeyRequirement for the description of resident_key’s values and semantics.
require_resident_key: boolThis member is retained for backwards compatibility with WebAuthn Level 1 and, for historical
reasons, its naming retains the deprecated “resident” terminology for [discoverable credentials].
Relying Parties SHOULD set it to true if, and only if, Self::resident_key is set to required.
user_verification: UserVerificationRequirementThis member specifies the Relying Party’s requirements regarding user verification for the
create() operation. The value SHOULD be a member of UserVerificationRequirement but
client platforms MUST ignore unknown values, treating an unknown value as if the member does
not exist.
See UserVerificationRequirement for the description of user verification’s values and semantics.