oid4vp-request-uri-jar

OpenID4VP authorization requests using request_uri are handled by supporting both GET and POST methods to securely pass and retrieve signed request objects across devices. This approach authenticates the Verifier and processes the request according to specification.

JWT-Secured Authorization Requests (JAR) in OpenID4VP are signed request objects used to securely transmit authorization parameters via a request_uri. They enhance security by ensuring the request's integrity and authenticating the Verifier requesting verifiable presentations.

Client identifier prefix schemes for Verifier identification use defined prefixes like redirect_uri, openid_federation, decentralized_identifier, verifier_attestation, x509_san_dns, and x509_hash. These prefixes define the specific syntax and mechanism for authenticating the Verifier during the authorization request.

Yes, you can use the POST method to pass request_uri for OpenID4VP authorization requests. This Skill manages the POST request_uri method, including the necessary response handling and Verifier proof of possession models for secure processing.

The best way to authenticate a Verifier requesting verifiable presentations is by using signed request objects via JAR and client identifier prefix schemes. This ensures secure transmission and validates the Verifier's identity through defined authentication models.

An aud claim in a signed authorization request object is required to explicitly define the intended audience of the JWT, ensuring the Wallet accepts the request. This prevents interception and replay attacks when passing requests across devices.