Local Redirect URI does not accept hyphen/minus

[the_devotional]

I am exploring n8n for AI workflows and I am using "self-hosted-ai-starter-kit" and I want to use the Spotify tool in my workflow. When configuring the credentials I get this Redirect URI:

  http://localhost:5678/rest/oauth2-credential/callback

Since this is a local docker setup it is not so simple to add support for https, so to conform to the restrictions in Spotify regarding http, I can change the host to 127.0.0.1. However, I still cannot use this URI because the hyphen/minus in (the unchangeable) oauth2-credential does not validate as secure in Spotify Developer Dashboard. I can't really see a reason for this character to be disallowed - is this a bug?

[Ximzend]

Hi @the_devotional 

I have tested your URI after changing localhost with 127.0.0.1, and it worked without a problem.

Could you please copy and past the error message you get, or take a screenshot?

[the_devotional]

Hello Ximzend!

Thanks for the quick response 🙂

Here are two screenshots from Chrome on MacOS. When the hyphen is present it is not possible to press the Add button, but without everything works as expected. I have also tried the same thing in Safari on MacOS without success.

[Ximzend]

Hi @the_devotional 

Thank you for the screenshot. I had to create a new app to get the same error.

I'll escalate it to the Spotify team.

[WaterRL]

Hello, any updates regarding this problem? I'm trying to use n8n with spotify but when I put: http://127.0.0.1:5678/rest/oauth2-credential/callback

the url still isn't accepted. How can I got with this?

[Mordicus]

Hello,

I am running into the same issue, unrelated to  this specific oauth2-credential URL, but similarly a hyphen issue (in my case, part of the callback URL contains ".../music-service/...").

Adding another voice here hoping to bump this issue up.

[Mordicus]

Hello @Ximzend, I know you are not a Spotify employee, but I was wondering if there was an update on this bug resolution.

This is currently preventing contributors from doing local development with Spotify in our project, as they cannot create new applications with the correct (and valid, I might add, INCLUDING the new localhost>127.0.0.1 change) callback URL.

[Ximzend]

Hi @Mordicus

I've reported it again, and this issue lies with the tech team now. Sadly, I can't say when it will be fixed.

Edit: Fixed since my last message.

[Ximzend · Accepted solution]

Hi everyone,

Thank you for your patience.

This issue has been fixed now.

[Mordicus]

Thank you for your intercession @Ximzend !

I can confirm it is now working fine.