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 some circumstances, it would be great to be able to establish a non-ephemeral connection between the verifier agent and the mobile wallet: an example could be accessing a service where the user is automatically requested for the appropriate proof-request directly to their wallet, without presenting a QR code, if they have already visited the website and have established a connection with the verifier.
To fully support this, changes are required both at the verifier (vc-authn) layer and at the client application level using it for authentication. This issue would only cover the requirements and changes for vc-authn.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
In some circumstances, it would be great to be able to establish a non-ephemeral connection between the verifier agent and the mobile wallet: an example could be accessing a service where the user is automatically requested for the appropriate proof-request directly to their wallet, without presenting a QR code, if they have already visited the website and have established a connection with the verifier.
To fully support this, changes are required both at the verifier (vc-authn) layer and at the client application level using it for authentication. This issue would only cover the requirements and changes for vc-authn.
Initial brainstorming/concepts described here: https://hackmd.io/@esune/B1DFUwEoP.
The text was updated successfully, but these errors were encountered: