Skip to content

OID4VCI with Digital Credentials API #410

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.

Sign up for GitHub

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

Jump to bottom
Open
Sakurann opened this issue Nov 4, 2024 · 4 comments · May be fixed by #476
Open

OID4VCI with Digital Credentials API #410

Sakurann opened this issue Nov 4, 2024 · 4 comments · May be fixed by #476
Assignees
@leecam
Labels
has-PR
Milestone
1.1 or later

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

@jogu
Copy link
Contributor

jogu commented Nov 18, 2024

This is the slides we used at IIW:

https://docs.google.com/presentation/d/1MJc33dmXb2Yip2neo0gbWilMUZ1vpCDq1Ucy48GFG34/edit?usp=sharing

Agree with all the points above from Paul/Kristina :)

@jogu jogu mentioned this issue Nov 30, 2024
Closed
@Sakurann Sakurann added this to the Final 1.0 milestone Jan 22, 2025
@Sakurann
Copy link
Collaborator Author

depends on the progress of DC API, but ideally, we should add text on using DC API for issuance in VCI spec before final

@Sakurann Sakurann modified the milestones: Final 1.0, 1.1 Mar 20, 2025
@jogu jogu added has-PR and removed ready-for-PR labels Apr 9, 2025
@jogu jogu linked a pull request Apr 9, 2025 that will close this issue
Open
@jogu
Copy link
Contributor

jogu commented May 1, 2025

Discussed on today's WG call. Would definitely be nice to have in 1.0 but we're lacking implementation experience. Could potentially add it during public review if we get the implementation experience - let's try and do an interop event on it to get the experience.

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

@leecam leecam

Labels
has-PR
Projects
None yet
Milestone
1.1 or later
Development

Successfully merging a pull request may close this issue.

Add support for the Digital Credentials API openid/OpenID4VCI
4 participants
@jogu @leecam @paulbastian @Sakurann