Discussion Type

Question

Discussion Content

Original issue, https://github.com/orgs/community/discussions/64224, is closed as dormant, and, understandable, as it is a niche, but its still a very "nice-to-have" feature. OP had an issue with Vercel, I have with Chrome extensions, and its driving me kinda mad for a few days now.

For example, Chromium extensions have unique set of ID's and, as extensions are not webapps, redirect URLs for OAuth is https://<extension_id>.chromiumapp.org. A unique ID is assigned once I register the app to Chromium Extension Store, and I will only have one callback url, which is, fine. Right. No. If you install the extension from Extension Store, callback url will work just fine, you will be redirected to the assigned unique ID. If you load the extension unpacked, from local files, in developer mode, you will have a random ID, which renders Github oauth useless because redirect URL does not match. So I cant test if Github works fine or not locally.

What is the solution for this? Creating separate app for every developer? Create separate copy of our backend (for exchanging the credentials for OAuth token) for every developer because github secret is different? Yes, this is a niche need, but, its so f**ing annoying. This could be just solved by https://*.chromiumapp.org.