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

Aperta
#2,629 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
38/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
postgresql, rust

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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)
Lingua principale
Rust
Stelle
2
Fork
0
Merge medio
9h 48m
PR unite (30g)
151

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di registrystack/registry-stack

Tutte le issue di registrystack/registry-stack

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.