Consent cap of self-registered MCP clients: let the user see and free what counts, and hold it under parallel consents

Aperta
#3,441 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
46/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp

Direzione di ricerca

Read the follow-ups #3397 and #3434 and inspect the consent cap, its prune logic, /me/sessions, UserSessions.ListAsync, and the auth rate limit. Add a way for users to identify and end the consents that count toward the cap, and ensure parallel consent requests cannot exceed it, or document the accepted overshoot in the spec. Add tests for both behaviors; the issue does not name test files.

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

Descrizione

area:identity plugin type:bug

Follow-ups of the cap on the self-registered MCP clients a user's consents keep (#3397, #3434), found in its review.

  • A user at the cap cannot see or free the consents that count. A valid consent whose tokens have expired still counts, since the prune keeps valid permanent authorizations, and /me/sessions does not list it (UserSessions.ListAsync needs a live token). A user whose client registers again at each install reaches the cap and then gets a bare invalid_request page, until an administrator removes a client or the user changes the password.
  • The cap is read before the insert. Parallel consent posts each pass the count, so the overshoot is the number in flight, bounded only by the auth rate limit of 20 a minute per address.

Wanted

  • A way for the user to see the consents to self-registered clients that count toward the cap and to end them, or a consent page that says what to do.
  • The cap held under parallel consents (the count inside the write, or a retry on conflict), or the accepted overshoot recorded in the spec.
  • Tests for each.

Found in the review of #3434. Bundle 26.

Lingua principale
C#
Stelle
567
Fork
107
Merge medio
1h 19m
PR unite (30g)
353

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 fluentcms/FluentCMS

Tutte le issue di fluentcms/FluentCMS

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.