Expand description
JSON Web Signatures (JWS)
The encoding and decoding APIs are strongly informed by the requirements of the higher level functionality
offered by the IOTA Identity library. Hence these APIs may possibly not be immediately recognizable from a standard
JWT/JWS perspective. See identity_jose/examples/jws_encoding_decoding.rs
for a complete example of how to encode
and then decode a JWS.
Structs§
- A JWS encoder supporting the Compact JWS serialization format.
- A cryptographically verified decoded token from a JWS.
- The
Decoder
is responsible for decoding a JWS into one or moreJwsValidationItems
. - An encoder supporting the Flattened JWS JSON Serialiazion format.
- An encoder for the General JWS JSON Serialization format.
- JSON Web Signature JOSE Header.
- A partially decoded JWS containing claims, and the decoded verification data for its corresponding signature (headers, signing input and signature). This data can be cryptographically verified using a
JwsVerifier
. SeeSelf::verify
. - An iterator over the
JwsValidationItems
corresponding to the signatures in a JWS encoded with the general JWS JSON serialization format. - Simple wrapper around a closure capable of verifying a JWS signature. This wrapper implements
JwsVerifier
. - The recipient of a JWS.
- Input a
JwsVerifier
verifies.
Enums§
- The requirements towards the character set when encoding a JWS.
- Options determining whether the payload is detached and if not which additional requirements the payload must satisfy.
- Supported algorithms for the JSON Web Signatures
alg
claim. - The serialization format used for the JWS.
- The cause of a failed jws signature verification.
Traits§
- Trait for cryptographically verifying a JWS signature.
Type Aliases§
- A General JWS Encoder that is currently processing the latest
Recipient
. - Error type for a failed jws signature verification. See
JwsVerifier
.