Forum Discussion

Anonymous's avatar
Anonymous
Apr 08, 2019
Solved

Running as different user in Domain joined desktop always uses current user.

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?

  • 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.

6 Replies

  • 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.

    • Anonymous's avatar
      Anonymous

      Eric_Lawrence 

       

      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.

      • Elliot Kirk's avatar
        Elliot Kirk
        Former Employee
        I just tried on the latest Canary build and I see the behavior that Eric_Lawrence is seeing, where Normal windows log me in automatically, and InPrivate windows ask for my creds. You can always install the Canary build side by side with the Dev build if you need this behavior today :-)
  • Thank you for your questoin, Deleted. I will pass on your four feedback. We are still making changes to the way we handle accounts, so keep updating and let us know what you think.
    • Anonymous's avatar
      Anonymous

      Elliot Kirk 

       

      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.

       

       

Resources