Expand description
RFC 9421 HTTP Message Signatures under the AAuth profile (AAuth §HTTP
Message Signatures), with the signer’s key named in Signature-Key
(draft-hardt-httpbis-signature-key).
sign covers @method, @authority, @path, @query when there is
one, signature-key, and for a request with a body content-digest and
content-type. verify checks a signature and hands back the key that
made it; a token in a jwt scheme is decoded but NOT verified — that is
crate::token::verify_token’s job, against its issuer’s keys.
Structs§
- Incoming
- A signed request as it arrived.
- Outgoing
- A request to sign, as its recipient will see it.
- Verified
- A signature that verified.
- Verify
Options - How
verifyjudges a signature. The default is now, a 60-second window either way, and Ed25519 or ES256.
Enums§
- Signature
Key - How the verifier finds the signer’s key: the
Signature-Keyscheme. - Signer
- What signed a request.
Constants§
- LABEL
- The label this crate signs under.
- SIGNATURE_
HEADERS - Request headers a signer sets, which a proxy signing on someone’s behalf should strip from what it was handed.
Functions§
- content_
digest sha-256=:…:, the RFC 9530Content-Digestofbody.- header_
map - The headers
signreturns, as aHeaderMapto send. - sign
- The headers that sign
requestwithkey, presentingsignature_key. - sign_
jwt signpresentingtokenunder thejwtscheme: how an agent signs.- verify
- Verify
request’s signature.resolveris consulted only for thejwks_urischeme.