Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Francesco Grauso <[email protected]>
  • Loading branch information
peppelinux and grausof authored Aug 8, 2023
1 parent 811430f commit f152527
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions docs/en/relying-party-solution.rst
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,7 @@ Remote Protocol Flow

In this scenario the Relying Party provides the URL where the signed presentation request object is available for download.

The Relying Party MUST detect the device type of the requestor (Wallet Instance), if it is a mobile device or a workstation, and activate one the supported remote flows:

Depending on whether the Relying Party client is on a mobile device or a workstation, it must activate one of the supported remote flows:
* **Same Device**, the Relying Party MUST provide a HTTP redirect (302) location to the Wallet Instance;
* **Cross Device**, the Relying Party MUST provide a QR Code which the User frames with their Wallet Instance.

Expand Down

0 comments on commit f152527

Please sign in to comment.