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

Abierto
#2,629 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
postgresql, rust

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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)
Lenguaje dominante
Rust
Estrellas
2
Forks
0
Merge medio
9 h 48 min
PR fusionados (30 d)
151

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de registrystack/registry-stack

Todos los issues de registrystack/registry-stack

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.