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

Ouverte
#3,441 1 commentaire 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é
4/5
Temps estimé
3-5 jours
Accessibilité débutants
46/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
csharp

Piste de recherche

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.

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

Description

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.

Langage dominant
C#
Étoiles
567
Forks
107
Merge moyen
1 h 19 min
PR mergées (30 j)
353

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

Toutes les issues de fluentcms/FluentCMS

Issues similaires

Plus d'issues C#

Recevez les nouvelles issues par e-mail

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