Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suport for 'request_uri' when response mode 'direct_post' is used #42

Open
hesusruiz opened this issue Jun 21, 2024 · 0 comments
Open

Comments

@hesusruiz
Copy link

hesusruiz commented Jun 21, 2024

Section 5.5 of openid-4-verifiable-presentations says:

5.5. Passing Authorization Request Across Devices
There are use-cases when the Authorization Request is being displayed on a device different from a device on which the requested Credential is stored. In those cases, an Authorization Request can be passed across devices by being rendered as a QR Code.

The usage of the Response Mode direct_post (see Section 6.2) in conjunction with request_uri is RECOMMENDED, since Authorization Request size might be large and might not fit in a QR code.

To enable future scalability of the complexity of Authorization Requests, VCVerifier must support 'request_uri'. To simplify implementation, it is better to always present Authorization Requests in QR codes using 'request_uri'.

This also reduces the size of the QR code with the current Authorization Request, and facilitates scanning by the Wallet and makes it more robust under different lightning conditions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant