Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Client credentials flow returns 401 invalid_client for registered app

已关闭
#598 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
半天
新手友好度
8/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃

调研方向

The payload names no file, test or code path; the only entry point is the token endpoint POST https://secure.soundcloud.com/oauth/token, which returns 401 invalid_client. Nothing here can be reproduced from the repository. The reporter asks whether the app credentials are active and whether the blank redirect URI or website matters, which only maintainers with account access can answer. Done means a maintainer confirms the cause, and the issue is not a code change for a newcomer.

由索引模型根据 Issue 内容生成。

描述

I’m testing the documented Client Credentials flow for a registered SoundCloud app and consistently receive HTTP 401 with error invalid_client.

Request:
POST https://secure.soundcloud.com/oauth/token
Authorization: Basic <Base64(client_id:client_secret)>
Content-Type: application/x-www-form-urlencoded

grant_type=client_credentials

The app’s website is https://quacktronic.com. Its redirect URI is blank. The request is made server-side from my local development environment; no redirect URI is sent.

Could you confirm whether the app credentials are active and enabled for the Client Credentials flow, and whether the app or its credentials may have been revoked? Does the app’s website or blank redirect URI affect this flow?

I can provide the app name or client ID through a private support channel if needed

主要语言
JavaScript
星标
260
派生
52
平均合并
1 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

soundcloud/api 的其他 Issue

查看 soundcloud/api 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。