rstack dev: issue application tokens so the Evidence application tutorial runs in replay

Aperta
#2,692 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
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
rust

Direzione di ricerca

Start by reading the run issuer and plan definitions that govern token grants; the issue does not name their files or tests. Decide whether development runs should mint application tokens and how declared clients’ scopes and claims are bounded before implementing the grant. Done means the Evidence application tutorial replays end to end without its test-skip, with the grant confined to the run and its TTL.

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

Descrizione

area:evidence area:platform

Problem

rstack dev runs an Evidence project, but its run issuer issues tokens only for a named test person (rstack dev token RUN --as PERSON) and for a declared browser application (authorization code with PKCE). It has no client-credentials endpoint.

The tutorial Request evidence from an application shows the one-call EvidenceClient.from_profile flow, where the application obtains its own token from the issuer. Against an rstack dev run that step cannot run, so for v0.47.0 the section is marked test-skip in the tutorial gate and says it needs a deployment. The client code stays covered by crates/registry-evidence-client/tests/against_a_real_deployment.rs and the Python and Node profile-exchange tests.

Proposal

Give the run issuer a client-credentials grant for clients the plan declares (scopes and claims bounded by the plan, as for people), then remove the test-skip so the tutorial replay exercises the application flow end to end.

Decide before building

Whether a development issuer should mint application tokens at all, and how the plan names those clients and bounds their scopes. This widens what a dev run's issuer can do; keep it confined to the run and its TTL.

Deferred until after v0.47.0.

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.