Skip to content

clarify batch issuance requirements #229

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

Merged
merged 5 commits into from
Sep 24, 2025
Merged

clarify batch issuance requirements #229

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
cd2e6fb
clarify batch issuance requirements
Sakurann Aug 1, 2025
fd22926
Apply Joseph's suggestions from code review
Sakurann Aug 19, 2025
30ba4ec
Apply suggestions from Paul's code review
Sakurann Sep 2, 2025
9a7dbf9
based on WG discussion
Sakurann Sep 3, 2025
e96862f
Apply suggestions from Oliver's code review
Sakurann Sep 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion openid4vc-high-assurance-interoperability-profile-1_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,7 @@ Both the Wallet and the Credential Issuer:

Both Wallet initiated and Issuer initiated issuance are supported.

The Wallet MUST support batch issuance. For each Credential Configuration, the Issuer MUST indicate whether batch issuance is supported by including or omitting the `batch_credential_issuance` metadata parameter. The Issuer’s decision may be influenced by various factors, including, but not limited to, trust framework requirements, regulatory constraints, applicable laws or internal policies.
The Wallet MUST support batch issuance. The Issuer MUST indicate whether batch issuance is supported by including or omitting the `batch_credential_issuance` metadata parameter. The Issuer’s decision may be influenced by various factors, including, but not limited to, trust framework requirements, regulatory constraints, applicable laws or internal policies.


Copy link
Contributor Author

@Sakurann Sakurann Sep 23, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For the Credentials with Cryptographic Holder Binding,
the Wallet MUST use the same Credential only once,
even when the claims being disclosed are the same.

Copy link
Contributor

@GarethCOliver GarethCOliver Sep 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This definitely shouldn't be true. (e.g. ZKP, already identifying responses etc).

## Issuer Metadata
Expand Down