Cannot access the client's own user information or tracks
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Title: Cannot access the client's own user information or tracks
Issue found of: October 5th, 2021
Endpoint(s):
GET /meGET /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.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
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.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100