Existing OAuth client became invalid and account was deleted after registering replacement credentials
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 10/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 领域
- api, authentication
调研方向
The payload names no source files or tests; it is an account-support request about OAuth 2.1 PKCE credentials and the /you/apps endpoint. Start by reading the repository's contribution and support guidance to find the private channel for account email, profile URL and client IDs, then route the report to SoundCloud API support. Done means the affected account and API application are restored or an official explanation is provided; do not attempt a code change from this issue.
由索引模型根据 Issue 内容生成。
描述
Hello SoundCloud API team,
We operate an established production integration using the SoundCloud OAuth 2.1 Authorization Code flow with PKCE.
On October 30, 2026, our existing API credentials suddenly stopped working. OAuth requests began returning an invalid_client / invalid client ID error, even though the credentials had previously worked normally and we had not intentionally changed them.
To restore service, we logged into the same SoundCloud account that owned the original API application and registered another API credential pair. Shortly afterward, the entire SoundCloud user account became unavailable or deleted—not merely the original API application. We can no longer access either credential pair through /you/apps.
Could you please clarify:
- Why were the original credentials invalidated?
- Could registering another application on the same account have triggered the deletion?
- Was this caused by the one-application-per-person policy or an automated security/enforcement process?
- Can the SoundCloud account and its API application be restored?
- Which private support channel should we use to provide the affected account email, profile URL and client IDs?
We can provide the affected client IDs and account information privately. We will not publish client secrets.
This has interrupted a live production integration, so we would appreciate help identifying the correct SoundCloud team or support contact.
Thank you.
- 主要语言
- JavaScript
- 星标
- 260
- 派生
- 52
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
soundcloud/api 的其他 Issue
-
难度 5/5 一周以上 新手友好度 8/100
soundcloud/api#615 ·
-
难度 3/5 半天 新手友好度 52/100
soundcloud/api#610 ·
-
难度 3/5 1-2 天 新手友好度 35/100
soundcloud/api#607 · 5 条评论 ·
-
难度 4/5 3-5 天 新手友好度 44/100
soundcloud/api#606 · 6 条评论 ·
-
难度 5/5 一周以上 新手友好度 25/100
soundcloud/api#605 ·
相似的 Issue
-
ready-for-agent
难度 2/5 1-3 小时 新手友好度 78/100
LucasSantana-Dev/Lucky#2945 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
brijeshb42/monaco-vim#175 ·
-
good first issue
难度 2/5 3-5 天 新手友好度 62/100
paipai1999/POS-system#3 ·
-
good first issue
难度 2/5 1-3 小时 新手友好度 85/100
r-afael/better-yt-recommendations#36 ·
维护者通常 1 天内回复
-
needs-triage
难度 2/5 1-3 小时 新手友好度 66/100
microsoft/playwright#43875 · 1 条评论 ·
维护者通常 1 天内回复