[WAL-896] feat(verifier2): expose authenticated request objects - #2055
[WAL-896] feat(verifier2): expose authenticated request objects#2055szijpeter wants to merge 1 commit into
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
33b2f8c to
28a6a7c
Compare
f6b304d to
ea22deb
Compare
8296069 to
437b624
Compare
38cab45 to
2a32e57
Compare
Co-authored-by: Cursor <cursoragent@cursor.com>
2a32e57 to
39481a2
Compare
|
|
Superseded by folding the WAL-896 identity stack into #2091, which now targets |



Summary
This PR isolates the verifier-side OpenID4VP Request Object changes needed by the WAL-896 stack. Signed cross-device sessions now expose an authenticated compact Request Object on the full authorization URL, while
request_uriPOST retrieval stays available for nonce-bound bootstrap.It is rebased onto current
mainafter walt-id/waltid-identity#2031 (WAL-1261 kid handling). The dependent wallet PR is walt-id/waltid-identity#1885. Enterprise CI companion: walt-id/waltid-identity-enterprise#604.What Changed
request_urifrom that URL.request_uri-basedauthorizationRequestUrlconstruction.request_urientry point for wallets that need nonce-bound POST retrieval.Verifier2RequestObjectKid.forClientand the original signing key, rather than comparing Crypto2 key IDs tokid.Architecture Notes
main:Verifier2RequestObjectKid,request_uriPOSTrequireMatchingKeyId, andsetup.withCoreKeyIfMissing. This PR does not replace that kid contract.requestJWT.Caveats and Follow-Ups
Breaking