Removing an organization member leaves the member's PATs and their policies behind
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 52/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- go
调研方向
Start in core/membership/org.go at cascadeRemovePrincipal and trace how RemoveOrganizationMember deletes the member’s organization policies. Compare that flow with the existing user-deletion path through userpat.Service.Delete, which marks a PAT deleted and removes its policies. The issue is done when removing a member also deletes that user’s PATs scoped to the organization and their policies, without affecting service users.
由索引模型根据 Issue 内容生成。
描述
What happens
RemoveOrganizationMember deletes the member's own policies for the organization, but it does not touch the personal access tokens (PATs) the member created for that organization, nor the policies those PATs hold. PAT policies carry the PAT id as principal, so the principal filter in the removal cascade (core/membership/org.go, cascadeRemovePrincipal) never sees them.
Why it matters
- The PAT grants nothing while the owner is out of the organization.
resource.Service.CheckAuthzchecks the PAT's own scope and then the owner's permission, and both must pass. - The organization's token list (
SearchOrganizationPATs) still shows the PAT with its role, as if it worked. - When the owner is added back, the old PAT works again at once, within whatever the owner's new role allows. Nobody re-issued or re-approved it.
- The PAT row and its policy rows stay behind for a user who is no longer a member.
Verified locally
- A member creates a PAT scoped to the organization with the viewer role. The PAT passes
CheckResourcePermission. - An owner removes the member with
RemoveOrganizationMember. The PAT now fails the check andGetOrganizationreturns permission denied, but its policy row is still live and the token list still shows the PAT with the viewer role. - The member is added back. The PAT passes the check again immediately.
Proposed fix
Run the PAT delete cascade for the member's PATs in that organization as part of the removal: list the user's PATs for the organization and, for each, call the same per-PAT delete that user deletion already uses (userpat.Service.Delete: mark the PAT deleted, then remove its policies). Only user principals are affected, since service users have no PATs.
- 主要语言
- Go
- 星标
- 344
- 派生
- 48
- 平均合并
- 2 天 10 小时
- 30 天内合并 PR
- 60
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
raystack/frontier 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 75/100
维护者通常 1 天内回复
-
难度 4/5 1-2 天 新手友好度 55/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 42/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 35/100
维护者通常 1 天内回复
查看 raystack/frontier 的全部 Issue
相似的 Issue
-
fix(handlers): explicitly set Content-Type header in static Index handler可能已有人在做 @kage-zero 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
Quick Open: restore dependency-directory exclusions in filesystem fallback可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
eugenioenko/ttt#1206 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
open-policy-agent/opa#9426 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
rorkai/App-Store-Connect-CLI#3192 ·
维护者通常 1 天内回复
-
t:urlDecodeUni does not map U+3002 and U+FF61 to a dot, unlike ModSecurity可能已有人在做 @fzipi 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复