Best way to handle OAuth to other services

[BarryCarlyon]

@xzion

I can have the config page include a link that takes the user to the Spotify OAuth landing. (And this will be loaded inside my frame on the Extension config page?)

I think you should be able to launch a popup actually.
Best to test and see.

Config panels often have to auth users with other systems, so it has to be done to support your application.

Or if Spotify support implicit auth, where the code is passed back a a #code=r58784758475847587 and tend to be less lenient on enforced redirectURI’s sometimes (IE: Your app does not use a server, such as a client-side JavaScript app or mobile app. This approach does not require a server that must make requests to the API. to nab some copy from the Twitch Docs)

@xzion

When they approve the OAuth, can I have Spotify callback to a route on my EBS like (/verify) with the oauth goodies.

Or back to the dashboard page itself

@xzion

Then I can have my EBS redirect back to the Extension config page. This works with localhost, but how do i know the URL of my config page once the extension goes live? Does twitch provide a static location on the CDN where the assets are stored?

Hmm that’s a bit complicated actually… It’s in the form of

Twitch[CLIENT ID]-[RELEASED/INSTALLED VERSION]/configure

So, yes but no.

@xzion

And then i just need to whitelist Spotify.com and my EBS url and it should be ok in terms of approval?

Unsure, what we have described here makes sense and appears to meet the guidelines but may be rejected, I’m not Twitch Staff.

Personally, two points:

a) What is your extension going to offer that is better than the Spotify Extensions that already exists Creator Dashboard (hmm I’m sure there was two, there is only one now)
2) When I need to pull now playing from Spotify, I usually tell people “link a last.fm account to your Spotify in the Spotify Client and just give me your last.fm username instead”