Consent cap of self-registered MCP clients: let the user see and free what counts, and hold it under parallel consents
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 46/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- csharp
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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/sessionsdoes not list it (UserSessions.ListAsyncneeds a live token). A user whose client registers again at each install reaches the cap and then gets a bareinvalid_requestpage, 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
authrate 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.
- 主要语言
- C#
- 星标
- 567
- 派生
- 107
- 平均合并
- 1 小时 19 分钟
- 30 天内合并 PR
- 353
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
fluentcms/FluentCMS 的其他 Issue
-
area:localization plugin type:bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
area:storage type:bug
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 1 天内回复
-
area:testing type:bug
难度 3/5 1-2 天 新手友好度 72/100
维护者通常 1 天内回复
-
area:api area:publishing type:feature
难度 4/5 3-5 天 新手友好度 55/100
fluentcms/FluentCMS#3473 · 1 条评论 ·
维护者通常 1 天内回复
-
area:storage plugin type:bug
难度 5/5 一周以上 新手友好度 35/100
维护者通常 1 天内回复
查看 fluentcms/FluentCMS 的全部 Issue
相似的 Issue
-
worldInstancedOccluderNode reads its appendix count as one byte, but it is a VLQ可能已有人在做 @spuddeh 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 78/100
维护者通常 1 天内回复
-
fix(ocr): compile the Tesseract-free pipeline with Tokio runtime可能已有人在做 @Goldziher 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
priority:P2
难度 2/5 1-3 小时 新手友好度 82/100
-
bug sev-5 vm
难度 2/5 1-3 小时 新手友好度 76/100
-
难度 2/5 1-3 小时 新手友好度 85/100