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
[EDIT 16.10.24] probably this requires websocket @puria
The verifier app, when running on mobile, needs Firebase to receive communications.
In order to run it as a web app, we need basically to:
1. In the Verifier:
expose a route like /verification and map it on the Slangroom script that currently executes what is returned from Firebase
maybe (maybe not) some work needs to be done pass the output into the notification/history array
the QR code must be generated differently, specifically:
{
"relying_party": "https://relying-party1.zenswarm.forkbomb.eu/relying_party/",
"t": "https://verifier.myserver.com/verification", <-- here goes the endpoint created above, with the URL that can be read from .env"exp": 1570000000,
"m": "w", <-- the "w" stands for "web" and this will help the Relying party understand how to communicate with the Verifier-web"request_uri": "https://admin.signroom.io/api/collections/templates/records?filter=%28id%3D%222rn9c5rfu54bwjw%22%29&fields=schema""sid": "abcde",
"id": "k86672rkeyfe9h7"
}
Some minor facelift must be done in the GUI to make it look ok on a 16:9 screen - but no sweat here :-)
2. In the Relying Party:
There should be an IF ("m" == "w") then {pass the response via REST to "t"}
And I guess that we're good to go
The text was updated successfully, but these errors were encountered:
[EDIT 16.10.24] probably this requires websocket @puria
The verifier app, when running on mobile, needs Firebase to receive communications.
In order to run it as a web app, we need basically to:
1. In the Verifier:
Some minor facelift must be done in the GUI to make it look ok on a 16:9 screen - but no sweat here :-)
2. In the Relying Party:
And I guess that we're good to go
The text was updated successfully, but these errors were encountered: