Apr 08 2019 11:49 AM
Apr 08 2019 11:49 AM
When a machine is domain joined, and browser is InPrivate the current user credentials are continually used rather than prompting and/or using new credentials.
This is something Edge and IE can handle well that Chrome never could. I see that the Chrome behavior has been inherited rendering it nearly unusable in scenarios where different accounts are used from the same desktop.
Any chance that removing Chromes windows credentials and replacing with Edge/IE is on the roadmap?
Apr 10 2019 10:53 AM
Apr 10 2019 10:59 AM
As a base test, use https://portal.azure.com and use the switch user menu on a domain based workstation. No matter how hard you try it always stays with the currently logged on user. Even when InPrivate. Contrast that with a non-domain machine, or and Edge based InPrivate session which just work.
Apr 10 2019 11:28 AM
Solution@Deleted Are you using the Dev build? Recently, the Edge Canary build was changed here to make it behave like legacy Edge such that Windows Authentication is set to manual in InPrivate mode.
Apr 10 2019 11:30 AM
Nice, assume that will be in the next dev, which is what I'm running.
Once that is there it will be my default. Nice job people.
Apr 10 2019 04:33 PM
Apr 10 2019 04:44 PM
Yes thanks. I have also verified that I am now able to use alternate credentials in the canary build now.
I'm all in :)
The 'sign in with a different user' feature in the actual web site doesn't work still, but the InPrivate is an acceptable workaround.
Thanks, I wasn't expecting this any time soon. Expectations exceeded!
Apr 10 2019 11:28 AM
Solution@Deleted Are you using the Dev build? Recently, the Edge Canary build was changed here to make it behave like legacy Edge such that Windows Authentication is set to manual in InPrivate mode.