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

Offen
#3,441 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
46/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
csharp

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
C#
Sterne
567
Forks
107
Ø Merge
1 Std. 19 Min.
Gemergte PRs (30 T.)
353

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus fluentcms/FluentCMS

Alle Issues in fluentcms/FluentCMS

Ähnliche Issues

Weitere Issues zu C#

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.