[feat] 支持一个账户绑定多个第三方登录渠道,避免单渠道异常封号后账号与仓库绑定一起锁死
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- authentication
Research direction
The payload names no files, tests or entry points, so first find where an account is created from a single OAuth identity and where the repository binding is attached to it. This is a design change: decide the account-to-identity model before writing code. Done means a second login provider can sign into the same account and see the same repository binding, and removing the last remaining provider is refused.
Written by the indexing model from the issue text.
Description
问题
当前 AstrBot Cloud 的账户与第三方登录渠道(GitHub / Google / 邮箱等 OAuth 身份)是 1:1 关系:账户本身几乎就是由这个渠道身份标识出来的,仓库绑定也挂在同一条链路上。
这带来一个不可恢复的失效路径:
- 用户用渠道 A 登录并绑定了插件仓库 R;
- 渠道 A 的第三方账号被封禁 / 被删除 / OAuth 授权被撤销 / 该邮箱不可用;
- 用户再也无法登录 AstrBot Cloud —— 因为系统只认渠道 A;
- 于是连"进入后台把仓库 R 换绑到渠道 B"这个自救动作也做不到;
- 最终只能走人工,而人工换绑又缺少可信的身份校验手段,风险很高。
也就是说:第三方渠道的一次封号,会直接等价于 AstrBot Cloud 账户的永久丢失,并且连带丢掉仓库绑定与插件发布能力。 这不是罕见边界情况——封号、账号被盗后申诉失败、公司/组织账号变更都是真实高频场景。
期望行为
核心诉求:把"账户"和"登录方式"解耦,账户是唯一主体,渠道只是登录入口(1:N)。
- 一个 AstrBot Cloud 账户可以绑定 多个 渠道身份;
- 任意一个已绑定渠道都可以登录到 同一个 账户,进入的是同一套数据、同一套仓库绑定;
- 某个渠道失效(封号/撤销)后,用户仍可用其余渠道正常登录,并在登录状态下把当前绑定的仓库更换为另一个可用仓库;
- 反过来,用户也可以在登录状态下主动解绑不再使用的渠道;
- 关键保护:账户不允许解绑到 0 个渠道,避免账户变成无法登录的孤儿。
- Dominant language
- No language data
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AstrBotDevs/astrbot-cloud-issues
-
[Bug]Openbug
Difficulty 3/5 1-2 days Newbie friendliness 46/100
-
[Bug] 自动安全检查失败Openbug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
给我解封吧求求了,我再也不乱发插件了Open
Difficulty 1/5 Under an hour Newbie friendliness 5/100
AstrBotDevs/astrbot-cloud-issues#32 · 2 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 15/100
All issues in AstrBotDevs/astrbot-cloud-issues
Similar issues
-
ready-for-agent
Difficulty 1/5 1-3 hours Newbie friendliness 79/100
gregwebs/agent-vm-images#216 ·
Maintainers usually reply within 1 day
-
Layout accepts a step threshold of 0 or less, then in-toto-verify crashes with StopIterationPossibly taken @BahaaMattar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenPrinting/cups#1826 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mongodb/kingfisher#588 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linuxhsj/openclaw-zero-token#302 ·