-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fetching OAuth access token returns 400 "invalid_grant" #341
Comments
Hey @stevereinvented, the redirect Uri is most probably the reason of this error, can you please share your username and app name so I can update the redirect uri for the application? |
Thanks for getting back so quickly, and sorry for the delay my side. The username is freshnet and the app is "Fresh On The Net Moderator". |
@youssefhassan is there an update on this? Still seeing the same error, and the URL still appears unchanged as beginning with http:// in https://soundcloud.com/you/apps. Thanks. |
Invalid grant can happen when using a wrong code verifier/code challenge pair |
I don't know if there was meant to be a link in your reply, but I use pkce-php for generating the code verifier / challenge. That seems to be working correctly, and as far as I can tell I'm following the correct steps as described above, so I'm still at a loss on this. |
Title: Fetching OAuth access token returns 400 "invalid_grant"
Issue found of: October 16th, 2024
Endpoint(s):
POST secure.soundcloud.com/oauth/token
Scope(s):
Application uses authorization_code workflow for authentication
Steps to reproduce:
After authorizing via https://secure.soundcloud.com/authorize with params:
…attempt to obtain an Access Token from https://secure.soundcloud.com/oauth/token with:
Expected behaviour:
The Access Token is returned as per https://developers.soundcloud.com/docs/api/guide#auth-code
Actual behaviour:
400 {"error":"invalid_grant"}
This had been working until last week (the issue was noticed on Oct 16), and there have been no changes on our our side.
If it's of any relevance, the redirect URL registered is http:// not https:// and that is what is passed, but the site is HTTPS now.
The text was updated successfully, but these errors were encountered: