Evidence: serve a credential status list and link it to source record changes

未关闭
#2,629 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
postgresql, rust

调研方向

Start by reading the existing status module and the OID4VCI issuance service, then inspect how Evidence definitions are validated by evidencectl check. Trace how source record changes are detected and how reinstatement approval is recorded. Done means the acceptance cases pass: issued credentials carry a status reference, changes update the served list within a defined bound, reinstatement stays pending until approved, and no per-credential lookup route is served.

由索引模型根据 Issue 内容生成。

描述

area:evidence criticality:p2 enhancement studio:product-gap

When a licence is suspended or revoked, the wallet credential issued for it still verifies until it expires. The status code exists as library code that the served runtime does not call, so there is no status list endpoint and nothing connects a change in the source registry to a status change. Authors can only keep wallet credentials short-lived and reissue them.

Smallest change

  • Serve the status list that the status module already produces (token-format list signed with the Evidence credential key) from the OID4VCI service, and add the status reference to issued credentials when the definition asks for it.
  • A status transition (valid, suspended, revoked) is driven by a named change on the source record, declared in the Evidence definition and checked by evidencectl check.
  • Moving a credential from suspended back to valid does not happen by itself: it raises a pending reinstatement that an operator approves.
  • The list carries no per-credential identifier a verifier can use to link credentials.

Acceptance

  • An issued credential carries a status reference, and the served list shows it valid; after the source record change it shows suspended or revoked within a stated bound.
  • A test shows a suspension lifted at the source leaving the credential suspended until the operator approval is recorded.
  • A test shows the list is the only thing served: no per-credential lookup route.
  • Definitions without status keep today's behaviour.

Out of scope

  • Withdrawing credentials already issued without a status reference.
  • Status for credentials issued by other issuers, and wallet-side behaviour.
  • Changing the approval rules for reinstatement.

Related

  • #568 (representative credential lifecycle), #57 (registry-backed OID4VCI issuance)
主要语言
Rust
星标
2
派生
0
平均合并
9 小时 48 分钟
30 天内合并 PR
151

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

registrystack/registry-stack 的其他 Issue

查看 registrystack/registry-stack 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。