Unable to use new Spotify OAuth provider
Hi there,
Earlier this week, my PR to add a new OAuth provider for Spotify was merged. (https://github.com/windmill-labs/windmill/pull/4581)
I've updated the docker images in my self-hosted instance to the release that includes this commit (1.412.0) so that I can try out the new provider.
I can configure the client ID and secret for a Spotify OAuth provider in the instance settings, so that seems to work correctly. However, when I try and create a resource of type Spotify, I get
Not found: ResourceType not found at name spotify and nothing happens after I complete the callback web form.
I tried running the "Synchronize Hub Resource types with instance" script but no new resource types are pulled. Is there something I need to do as a contributor to make a spotify resource type available?
Thanks for your help :)
10 Replies
You need to suggest it to hub.windmill.dev and we will approve it
But you can just add it manually to the admins workspace for now
Make sure to have a token field and the name to be exactly spotify
+ resource type, on ressources page
Got it, I will try this. Thanks
Hey again, picking this back up now that I have more time. I took your advice and created the resource type. Now, when I go through the oauth flow, no resource is actually created. Is this because I'm not using EE?
I should add that no errors seem to be logged in windmill-server (all API calls return non-4xx/5xx)
it's not because you're not EE no
got it. any places you'd recommend I check for possible issues? The correct callback route is
/oauth/callback/spotify right? Is it possible to enable debug logs for the windmill server?I will give it a try myself and let you know if it works
Might be easier if you give me temporary client id/secret id then you revoke access once I'm done with the test
Sure, let me DM those to you in a minute
You will need to set callback url to localhost:3000 as well
does it need to be
localhost:3000/oauth/callback/spotify?
solved: I had a browser extension that was interfereing with the oauth flow for some reason