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

OID4VCI with Digital Credentials API #410

Open
Sakurann opened this issue Nov 4, 2024 · 1 comment
Open

OID4VCI with Digital Credentials API #410

Sakurann opened this issue Nov 4, 2024 · 1 comment

Comments

@Sakurann
Copy link
Collaborator

Sakurann commented Nov 4, 2024

we added support to use OpenID4VP over Digital Credentials API, it would be beneficial to add support to use Digital Credentials API for VCI, too, when passing a credential offer. it would greatly help with wallet selector. Not so much with cross-device security, since credential offer is not signed, but adding an origin information to the credential offer might help already?

This was discussed at IIW and since the wallet matcher needs enough information to make a decision whether the wallet can support a credential offer from a specific issuer, and wallet matcher cannot make an external call, the preferred direction seems to be to add entire issuer metadata and authorization server metadata by value to the credential offer, when it is passed over the browser API. and the wallet can make its own decision which issuer it can talk to, based on that information.

@paulbastian
Copy link
Contributor

I support adding both metadata as optional parameters to Credential Offer.

We should make clear that this is currently intended to enable an offline credential selector/matcher. The Wallet should make sure that the metadata is authentic and probably fetch it on their own after wallet invocation

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

2 participants