[Openid-specs-digital-credentials-protocols] Request for VCI implementor feedback: Mandating credential_configuration_id in Credential Request when using scopes

[Joseph Heenan]

Hi all

Some of you might remember that Paul made a lot of good suggestions around improving/simplifying the VCI spec around 6 months ago, which where then discussed & refined in WG meetings:

https://github.com/openid/OpenID4VCI/issues/294


The final change to be made is using credential_configuration_id in Credential Request when using scopes:

https://github.com/openid/OpenID4VCI/pull/392

We would like feedback from implementors/other interested parties on whether we should add this an a third option in addition to the two already shown in https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html#name-credential-request or if we can remove the existing option where “format” is used. The primary reason to remove would be to keep the specification smaller/simpler and more interoperable, in the same way as has already be done (since ID1) for RAR requests

For clarity, this would NOT require that credential_configuration_id are listed in the issuer metadata, it is still fine to communicate these out of band to the client in the same way as can already be done for scope / format / type values.


We hope to make a final decision on the 1st October WG call, so if you have questions/an opinion please either provide feedback by then (on the above pull request or by responding to this email) or join that call.

Many thanks

Joseph

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20240923/4b5550f2/attachment.html>