Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Presentation within the Issuance: Webview vs embedded http client without js #503

Open
4 tasks
peppelinux opened this issue Nov 20, 2024 · 2 comments
Open
4 tasks
Assignees
Milestone

Comments

@peppelinux
Copy link
Member

peppelinux commented Nov 20, 2024

Using Webviews, when the presentation phase is required during the issuance for user authentication, we satisfy the following points:

  • More possibility in be compliant with issuances flows implemented by credential issuers not linked to the italian public services
  • Compliance with Credential API
  • Compliance with the current presentation flow documented within the v0.8.2 of the current specs
  • Compliance with the possibility of using User's interaction for selecting the credential id (in between the token endpoint response and the next credential request)
@RosaliaGaleano
Copy link
Collaborator

FYI @AntoPaparella

@RosaliaGaleano
Copy link
Collaborator

We assume that the webview flow starts after the person identification data presentation step and ends before the PIN request step.
Define whether the user is redirected out of his wallet instance to an interface owned by the issuer or whether the frontend flow remains unchanged from the current one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

3 participants