Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.
09-20-2019 12:07 PM
On MacOS/latest, Safari/latest (plus going back in time 4 years). This problem has always plagued me, yet does not seem to be a mentioned problem. Basically, I have many instances of Neo4j 3.4.x and 3.5, local and cloud, and the issue happens with all of them.
When I try to Sign In for Browser Sync, it will launch a separate Auth window, but then that window auto-closes before I can interact with it. Every once in a while, I can actually complete the process and sign in, but it's rare. I believe I've struggled a little in Chrome as well, but not to the same degree.
Does anyone else ever see this? Seems like it's just me (but like I say, it's been going on for years).
10-08-2019 02:10 PM
Yes, this just happened to me as well on OS X and Chrome.
Before I tried to sign in, I cleared my Chrome console history. Then I clicked the checkbox and the sign-in button, and I got this warning twice in the console (no errors):
A cookie associated with a cross-site resource at http://auth0.com/ was set without the SameSite
attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None
and Secure
. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
A few minutes later, the Sign-In button appeared again (or maybe it never disappeared) and when I clicked it, the Auth0 dialog stayed up so I could complete and submit it. There were no more warnings this time.
All the sessions of the conference are now available online