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

Support mulitple proofs to the Credential Endpoint #91

Closed
5 tasks
dtsiflit opened this issue Oct 18, 2024 · 0 comments
Closed
5 tasks

Support mulitple proofs to the Credential Endpoint #91

dtsiflit opened this issue Oct 18, 2024 · 0 comments
Assignees
Labels
draft14 Feature in Draft 14 of the specification openid4vci alignment

Comments

@dtsiflit
Copy link
Contributor

After draft 13 and the removal of batch endpoint, Credential endpoint was updated to receive either a single proof (of possession) or multiple proofs. In the later case, multiple credentials (single credential_configuration_id, same dataset, different device keys) should be returned to the response.

  • Add a new attribute to issuer's metadata named batch_credential_issuance. Attribute is optional and contains a single attribute batch_size which is required. Details
  • Change Credential Request to contain either a proof or a proofs attribute (not both). Details
  • Simplify the internal hierarchy that represents a credential request. The Single and Batch instances are no longer needed.
  • Change the issuance interface to allow caller to pass one or more PopSigner
  • In the later case, check metadata batch_credential_issuance
@dtsiflit dtsiflit added openid4vci alignment draft14 Feature in Draft 14 of the specification labels Oct 18, 2024
@dtsiflit dtsiflit self-assigned this Oct 18, 2024
@dtsiflit dtsiflit mentioned this issue Nov 25, 2024
10 tasks
@dtsiflit dtsiflit closed this as completed Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
draft14 Feature in Draft 14 of the specification openid4vci alignment
Projects
None yet
Development

No branches or pull requests

1 participant