Hey Barry, thanks for the help.
So I think I misunderstood what I could and couldn’t do in regards to linking offsite in an extension.
Let me get this straight.
- 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?)
- When they approve the OAuth, can I have Spotify callback to a route on my EBS like (/verify) with the oauth goodies.
- 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?
- And then i just need to whitelist Spotify.com and my EBS url and it should be ok in terms of approval?
If that works that’d be sweet. Would appreciate further clarification the points there if you don’t mind.
Cheers