In this section the following flows are described:
Same Device Flow, where the Verifier and the Wallet Instance acts in the same device.
Remote Same Device Flow, where the Verifier and the Wallet Instance acts in the same device.
Remote Cross Device Flow, where the Verifier and the Wallet Instance acts in different devices and the Verifier is a remote Relying Party.
The flows are analyzed in this chapter, taking into account security and privacy considerations.
@@ -1031,21 +1029,17 @@Note
Relying Party and Verifier are the same entity.
-In the Same Device Authorization Flow, the User interacts with a Verifier that resides in the same device of the Wallet Instance. -This scenario utilizes HTTP redirects to finalize the authorization phase and obtain Verifiable Presentation(s).
-Note
-This flow will be described more in detail in future releases of this documentation.
-In the Cross Device Authorization Flow, the User interacts with a remote Relying Party. -This scenario requests the Verifier to show a QR Code which the User frames with their Wallet Instance.
+In the Same Device and Cross Device Authorization Flows, the User interacts with a remote Relying Party. +This scenario requests the Verifier to provide the URL where the signed request object is available.
+The Verifier MUST detect the device type of the requestor (Wallet Instance), if it is a mobile device or a workstationm and activate one the supported remote flows:
+In the Same Device* flow the Verifier MUST provide a HTTP redirect (302) location to the Wallet Instance;
In the Cross Device* flow the Verifier MUST provide a QR Code which the User frames with their Wallet Instance.
Once the Relying Party authentication is performed by the Wallet Instance, the User gives the consent for the release of the personal data, in the form of a Verifiable Presentation.
- +