View the original community article here
Last tested: Nov 4, 2019
This is a change made in Chrome version 80. Looker has made the necessary change to cookies on our end, however, we work with some vendors, such as Doubleclick, that have not made the change yet.
The last Looker version that does NOT have the necessary change to our cookies is 6.24.6. Anything after that (6.24.7+, 7.x) should have the fix.
Instances started with the no-ssl flag may not set the necessary cookie directives. If self-hosted customers are using this flag to do ssl termination at their load balancer, they should instead use the ssl-provided-externally-by flag. See list of startup flags.
This content is subject to limited support.