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

Cannot access the client's own user information or tracks

未关闭
#147 5 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞

调研方向

Start with the linked SoundCloud API documentation and the OAuth token flow, then investigate the reported GET /me and GET /me/tracks requests using client_credentials tokens. Done means determining whether those endpoints support this grant type and documenting or resolving the 401 behavior with a clear explanation and reproducible result.

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

描述

question

Title: Cannot access the client's own user information or tracks

Issue found of: October 5th, 2021

Endpoint(s):
  • GET /me
  • GET /me/tracks
Steps to reproduce:

Using the client_credentials grant type we receive an access token from the oauth/token endpoint which we use immediately to try and retrieve the users data and tracks from the /me and /me/tracks endpoints.

In both cases a 401 unauthorized response gets returned.

Based on this paragraph from the docs we are led to believe that as long as we're only trying to access the user details of the owner of the app (client Id & secret) this should be possible:

Authenticating without the SoundCloud Connect Screen
If you simply need an access token for testing, and do not want to go through the connect flow, or if your app needs to access only public resources, you can use the OAuth Client Credentials Flow. An example of this kind of app would be an artist's website where you'll only be accessing their tracks, playlists, or user information. In these cases you may exchange a set of your client credentials for an access token.

Expected behaviour:

The users details and tracks should be returned.

Actual behaviour:

401 unauthorized response every time without any error message.

主要语言
JavaScript
星标
253
派生
53
平均合并
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 摘要。