Need a valid "redirect_uri" to get my access token
hartmannn opened this issue · 16 comments
I'm following the procedure to get my access token, and the first dialog asks for three parameters including an URL, which isn't indicated in the instructions.
So could you please complete this URL for me ? (ie replace YOUR_REDIRECT_URI) ::
https://connect.deezer.com/oauth/auth.php?app_id=247082&redirect_uri=YOUR_REDIRECT_URI&perms=basic_access,email,manage_library
Thank you very much
Hi @hartmannn,
If I remember correctly, this redirect uri is only used when using the deezer web api, to redirect user once authenticated. This is not our use case obviously because we are building a native player, so I think you can use whichever url you want to (I think I used the url of my github page).
Hope it helps
Thank you @blackccpie for your quick answer,
I tried https://connect.deezer.com/oauth/auth.php?app_id=247082&redirect_uri=https://github.com/blackccpie&perms=basic_access,email,manage_library as advised and got the following error message : You must specify a valid request_uri.
On Deezer's documentation it is stated : " redirect_uri must be in the same domain as the domain you defined when you created the application" and that this parameter is mandatory.
Do you have any idea?
when you created your App, which domain did you use?
For exemple if you used .deezer.com then your redirect uri should be something like deezzy.deezer.com (no matter if this is a dummy url).
I didn't create an app, I chose instead to keep the deezzy app id :"247082". So which domain did you use?
ok so I used the .deezer.com domain, can you then try with deezzy.deezer.com redirect uri?
Hum, strange... I'm gonna make some tests and keep you updated. But I admit this part is not crystal clear in my documentation (as well as in Deezer's doc).
in fact forget about the domain thing, this url should work:
https://connect.deezer.com/oauth/auth.php?app_id=247082&redirect_uri=http://www.github.com/blackccpie&perms=basic_access,manage_library,email
you forgot the www. in your previous try
your key should be at the end of the new page url
It works! Thank you very much!
In fact I'm sure that I'm not the only one to ask myself this question, because it was already asked at the end of an article about your work published in a french website.
For the next step I must fill this URL :: https://connect.deezer.com/oauth/access_token.php?app_id=YOU_APP_ID&secret=YOU_APP_SECRET&code=THE_CODE_FROM_ABOVE
Deezer's documentation : "The app secret is available from the Application setting page and should not be shared with anyone or embedded in any code that you will distribute (you should use the client-side flow for these scenarios)"
I guess I will have to register your application under an other name. Doesn't it bother you? Can I use the GitHub page of Deezzy as link to "my" terms of use?
No problem for me if you create your application under another name.
I should remove the case where one use the same app id as I did from my doc, that's not a proper scenario.
@hartmannn : I'd be curious to know if you got the whole thing working, please let me know
OK, I will
Thank you @blackccpie & @hartmannn. I got Deezzy working with my account thanks to your exchanges here. =oD Been waiting a long time to use Deezer on my Raspberry Pis!
@tyrower : great, glad to hear that!
help me please, what exactly i should write in redirect -_- i tried on http://localhost:3000/, and its failed,tried on https://muz-project-gray.vercel.app/ and had the same( i tried with htttp, https, with no htttp\s ... same result ( ivalid redirect url and no deezer code :c