Issuer metadata pagination / limiting the number of credential_configurations_supported being returned
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
If the Issuer has a large number of credentials it supports (thousands or millions), and if it returns all of them to the wallet when the wallet fetches the metadata, the wallet might fail. I don't think the standard will set the upper limit to the credentials to be returned as it is the implementation detail (meaning each implementation is free to set the limit that it believes is reasonable), but we should probably add security considerations in the specification that issuers are recommended to add this limit.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the issuer metadata and security considerations sections in the specification, then review how credential_configurations_supported is described. Add a recommendation for issuers to limit the metadata returned when many credentials are supported, and verify that the guidance reflects implementation-specific limits.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100