my website has “Login with Twitch” capability via oAuth. i am looking to integrate it into our Chrome extension, now.
the Chrome Identity API has a method for handling redirect urls since your extension naturally does not have a FQDN- so chrome requires oAuth redirects to resolve to a variation of: https://*.chromiumapp.org/provider_cb
i’ve read a similar query, Multiple Sub-Domains with the API, where the suggested solution was to create an intermediary page. unfortunately that is not an option here, because chrome controls the single callback URL we have available to us.
Facebook integration worked out- because Facebook allows multiple callback URLs. what options do i have to handle this for Twitch?