Ignore thirdparty and advertizing cookies (set by Slack on browser login) #158
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rusq
changed the title
rusq
added a commit
that referenced
this pull request
Nov 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While investigating some other issue, and using EZ-Login 3000 with "email login" feature, i started getting strange errors that I've never seen before:
This did not happen when user/password login type was used.
Observing browser behaviour, stepping through debugger, and examining the cookies revealed the following: after successful workspace login with email method (slack sends an email with the code to enter on the login page), slack opens another tab of the [puppet] browser, which quickly sets all advertizing and tracking cookies.
Some facts:
The solution is - to cut them off after we grab the cookies from [puppet] browser.