In one of my brighter moments, I decided that The Thing To Doâ„¢ was clone a developer sandbox without enabling enhanced domains so that I could figure out the SSO implications.
As a bonus, now I have two more or less identical sandboxes so I can compare side by side. And initially I was trying to blame this behavior on Enhanced Domains because the message I got was
"We can't display this page because your browser blocks cross-domain cookies, but you can view this page in Salesforce Classic. Click here to open this page in Salesforce Classic."
But as it turns out, this happened in both sandboxes, so Enhanced Domains didn't cause the problem, but it also didn't fix it. Which I thought was the point of the exercise.
The steps to reproduce are:
- Open a new Incognito Window (Chrome -- I haven't tested this in Firefox or Edge yet).
- Navigate to Setup -> Users -> Users/Profiles/Permission Sets... take your pick*.
The URL is correct -- with or without the .sandbox. but you get this message. And it's correct, you can open it and do whatever you need to in Classic. But what I'm not getting is why this particular collection of circumstances always leads to this conclusion.
It's not so much a "problem" as "something I'm not quite understanding" and (might not even if it were explained). Specifically (a) what causes it, and (b) what prevents enhanced domains form resolving these use cases?#
*Permission Set Groups did not exhibit this behavior because a while back I had opt enable the agility to expire a permission set group, and part of that process was converting that page to Lightning UI, which doesn't have this conflict.
I've only just come across this when searching for a solution to the same issue in incognito mode, for the users list in setup. With the pointers here and elsewhere, it turns out that Chrome incognito does indeed block cross-domain cookies by default:
https://support.google.com/chrome/answer/9845881?hl=en#zippy=%2Chow-incognito-mode-works
And the fix of enabling them via the site settings sliders in the URL bar does resolve it:
Hope this helps (belatedly!) anyone else looking at this.