Clarify re-issuance pattern when evidence freshness changes
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
We're implementing OpenID4VCI for credentials where the underlying evidence has its own freshness window. For example, the issued credential may still be valid, but the source evidence behind it is refreshed every 30 days.
The refresh section notes that an issuer may signal the wallet to request refresh, but that signaling mechanism is out of scope.
For this case, is the recommended implementer pattern to treat the update as a new Credential Offer when the wallet does not already have a valid refresh token? Or are implementations expected to handle this entirely outside OpenID4VCI?
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 reading the refresh section and its statement that the signaling mechanism is out of scope. Compare that guidance with the new Credential Offer and refresh-token cases described here, then document the recommended implementer pattern and whether the behavior belongs within OpenID4VCI.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100