Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

launchWebAuthFlow & trust... #7

Open
wadabum opened this issue Mar 1, 2022 · 0 comments
Open

launchWebAuthFlow & trust... #7

wadabum opened this issue Mar 1, 2022 · 0 comments

Comments

@wadabum
Copy link

wadabum commented Mar 1, 2022

Hi, please consider removing the usage of chrome.identity.launchWebAuthFlow.

  • you can replace it by either just grabbing my cookie (or however they do it)
    (Live Followlist for Twitch appears to work this way)
  • or opening the flow in ACTUAL tabs so Addressbar & similar are visible.
    -- "serverless" there was some black magic about return-urls&extensionIDs,
    -- "with server" a simple JS landing to trigger a chrome.runtime.sendMessage(extensionID, ... ) should do it

Users have been trained for years to pay attention to domains, HTTPS and using password-managers,
this stupid popup chrome opens breaks all of those in the worst way possible.

Most importantly, it also seems to enforce "manual sign-in" on twitches end?
So even the "open the site yourself, login manually, now re-click the apps auth-button and see that you are logged in already" does not seem to work

launchWebAuthFlow is nice if "you want to login into a google account"
(AND you are also logged in with chrome itself into that very same google-Account)
- but for anything else its spooky a.f.

And by the looks they dont intend to change this (2014) https://groups.google.com/a/chromium.org/g/chromium-extensions/c/g82Gfx0m9P8

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant