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

Aberta
#3,441 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
46/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
csharp

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
C#
Estrelas
567
Forks
107
Merge médio
1h 19min
PRs com merge (30d)
353

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de fluentcms/FluentCMS

Todas as issues de fluentcms/FluentCMS

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.