You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We will implement JWT decoding and validation for the Provider struct. This will involve decoding the JWT and verifying its signature to ensure its authenticity. Additionally, we will perform other validation checks such as checking the issuer and audience claims.
Motivation
When a SiopRequest is particularly large (for example when it includes a Presentation Definition for Verifiable Presentations, or many claims) a Relying Party may choose to send its request by value by utilizing the request_uri. The actual SiopRequest that can be retrieved by following this redirect uri may or may not be encoded as a JWT. Therefore, the Provider should be capable of decoding and validation JWT's
Description
We will implement JWT decoding and validation for the Provider struct. This will involve decoding the JWT and verifying its signature to ensure its authenticity. Additionally, we will perform other validation checks such as checking the issuer and audience claims.
Motivation
When a
SiopRequest
is particularly large (for example when it includes a Presentation Definition for Verifiable Presentations, or manyclaims
) a Relying Party may choose to send its request by value by utilizing therequest_uri
. The actualSiopRequest
that can be retrieved by following this redirect uri may or may not be encoded as a JWT. Therefore, theProvider
should be capable of decoding and validation JWT'sResources
SIOPv2 section 9.
To-do List
Provider
struct.The text was updated successfully, but these errors were encountered: