[Spec Impl] Update QR code data to help INTENT based app launch

krishnakumar4a4 commented 1 year ago

Background

The QR code structure used in INJI is a JSON with two fields. one of the field "cid" is holding dummy value and another field "pk" holds the hex encoded advertisement payload of verifier. {"cid":"ilB8l","pk":"4f56504d4f5349505f2f9377eb06"}

What should be done

We will implement the format of QR code data mentioned in specification. We need to put 32bytes of pubkey in QR code data to be compatible with IOS as well. Do not use JSON as we need the QR code data to be used or enabling deeplinks.

OPENID4VP://connect?name=STADIONENTRANCE&key=8520f0098930a754748b7ddcb43ef75a0dbf3a0d26381af4eba4a98eaa9b4e6a&nonce=6e91ab1b48396d3e

Points to Note

Make sure it doesn't impact GNB implementation (or any other INJI implementation like Login with QR etc)
nonce to be used in QR code is yet to be decided as we don't have the concept of nonce being shared from Verifier side today

Sujithbn commented 1 year ago

This will be taken post 0.9 release

ravikp commented 1 year ago

Intent based launching can be taken as a feature post 0.9 release, but changing the QR code data format can be done before release.

Pragya279 commented 1 year ago

This requirement has been moved to Jira. Link to Jira ticket: https://mosip.atlassian.net/browse/MOSIP-26912

mosip / tuvali