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
In the (Q)EAA Issance flow as defined in the PR #70, we require the Issuer to perform a PID presentation request to the Wallet Instance according to [OpenID4VP] following a same-device flow. In the current version of the IT Wallet specification we only have defined a cross-device authorization flow.
We should add technical details in the Same Device Flow Section.
The text was updated successfully, but these errors were encountered:
The following non-normative example of an Authorization Request refers to the Authorization Request Object
from above through the request_uri parameter. The Authorization Request can be displayed to
the End-User either directly (as a link) or as a QR Code:
https://wallet.example.com?
client_id=https%3A%2F%2Fclient.example.org%2Fcb
&request_uri=https%3A%2F%2Fclient.example.org%2F567545564
I'll do a PR asap for enabling this in the current specs
In the (Q)EAA Issance flow as defined in the PR #70, we require the Issuer to perform a PID presentation request to the Wallet Instance according to [OpenID4VP] following a same-device flow. In the current version of the IT Wallet specification we only have defined a cross-device authorization flow.
We should add technical details in the Same Device Flow Section.
The text was updated successfully, but these errors were encountered: