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).
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 Chrome Platform Status and Chrome Platform Status.
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.
I was almost able to get Auth0 login working for Neo4j Browser Sync. The steps below are for Firefox, although I replicated this with similar ones on Edge.
After clicking the green "Sign In / Register" button, the autho.neo4j.com window pops up with the login page.
In the upper left, next to the un-editable address bar, are icons with info about the page. Click the (shield) to see the "Protections for auth.neo4j.com" settings.
Use the toggle to turn off "Enhanced tracking protection."
That allowed me to log in. Yay! Unfortunately, after a few seconds, the Neo4j Browser Sync sidebar shows Sync service is down. Refreshing the page or opening a new window with the page shows the same or just shows that I'm not connected and need to login again.
All the errors in the Console relate to content-security-policy, cross-site scripting, SameSite attribute, and failure to postMessage on DOMWindow. These are all familiar from my own web development struggles and have to do with how content is stored/passed between disparate parts of a webpage.
It looks like Neo4j Browser Sync is no longer maintained and thus has not been updated for more modern web security standards. Too bad.
(shield) to see the "Protections for