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

Issues with Use Case - Wallet-Initiated Issuance after Installation #424

Open
javereec opened this issue Dec 5, 2024 · 0 comments
Open

Comments

@javereec
Copy link
Contributor

javereec commented Dec 5, 2024

When almost accidentally reading this section, I noticed some issues with it

The End-User installs a new Wallet and opens it. The Wallet offers the End-User a selection of Credentials that the End-User may obtain from a Credential Issuer, e.g. a national identity Credential, a mobile driving license, or a public transport ticket. The corresponding Credential Issuers (and their URLs) are pre-configured by the Wallet or follow some discovery processes that are out of scope for this specification. By clicking on one of these options corresponding to the Credentials available for issuance, the issuance process starts using a flow supported by the Credential Issuer (Pre-Authorized Code flow or Authorization Code flow).

Wallet Providers may also provide a market place where Issuers can register to be found for Wallet-initiated flows.

  • The language makes this hard to read and understand (e.g. "a selection of Credentials that the End-User may obtain from a Credential Issuer", "the Wallet or follow some discovery processes"
  • The last sentence does not even make sense to me.
  • References a term "Wallet Provider", which is not defined

My suggestion would be to remove this section or rewrite it completely.

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

No branches or pull requests

1 participant