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
This was required in 18013-7, but not in HAIP / OID4VP encryption profile. This makes associating the encrypted response to the request harder. It seems a comment pattern is to create an unique response uri for every request so that you always have the associated request.
This won't work for x509_san_uri, but this will probably be removed from the specification.
I think we should at least allow providing the authorization request beforehand to the library, and we can remove the callback to the the openid4vp request. You need to know the request associate with the response beforehand.
This was required in 18013-7, but not in HAIP / OID4VP encryption profile. This makes associating the encrypted response to the request harder. It seems a comment pattern is to create an unique response uri for every request so that you always have the associated request.
This won't work for x509_san_uri, but this will probably be removed from the specification.
See issue openid/OpenID4VP#441
This is causing issues with the Multipaz wallet from Identity Credential
The text was updated successfully, but these errors were encountered: