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

Ouverte
#2,629 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
38/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
postgresql, rust

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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)
Langage dominant
Rust
Étoiles
2
Forks
0
Merge moyen
9 h 48 min
PR mergées (30 j)
151

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de registrystack/registry-stack

Toutes les issues de registrystack/registry-stack

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.