Implement the SIOPv2 protocol into the Agent. Similarly to the OpenID4VCI implementation, the agent must have a method to generating an auth_request that can be displayed by the "Front-end" (of the implementer) as a QR-code. Further SIOPv2 interactions must be exposed via proxies. Lastly, the SIOPv2 flow must notify the results as an "event" towards the "Back-end" (of the implementer). This result must at least include the identity of the user that logged in.
Feel free to add missing information or ideas to this issue.
Motivation
Add to SSI capabilities by supporting decentralized login with DIDs.
Description
Implement the SIOPv2 protocol into the Agent. Similarly to the OpenID4VCI implementation, the agent must have a method to generating an
auth_request
that can be displayed by the "Front-end" (of the implementer) as a QR-code. Further SIOPv2 interactions must be exposed via proxies. Lastly, the SIOPv2 flow must notify the results as an "event" towards the "Back-end" (of the implementer). This result must at least include the identity of the user that logged in.Feel free to add missing information or ideas to this issue.
Motivation
Add to SSI capabilities by supporting decentralized login with DIDs.
Resources
No response
To-do List