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

"Block third-party authorization header" further clarification on UI #2491

Closed
planet0 opened this issue Mar 10, 2019 · 1 comment

Comments

Projects
None yet
4 participants
@planet0
Copy link

commented Mar 10, 2019

I noticed in the description for "Block third-party authorization header" that it mentions that it may require re-entering credentials in web forms, but enabling this in Stealth Mode affects more.

It seems to break safe Chrome extensions that require logging into third-parties, like Checker Plus for Gmail that checks mail.google.com on push, and also the Lastpass extension when going into Account Settings that use auth details from lastpass.com. Both are impossible to use with this option enabled.

Perhaps the description of this setting could warn users on how much this option could break extensions and add-ons used on Internet Browsers?

@ameshkov ameshkov added this to the 7.0 milestone Mar 10, 2019

@northis

This comment has been minimized.

Copy link
Member

commented Apr 18, 2019

Resolved in adguard-windows/pull-requests/399

@zzebrum zzebrum closed this May 22, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.