Forum Discussion
Jussi Palo
May 05, 2020Iron Contributor
edge://flags/#edge-windows-credentials-for-http-auth gone
Hi, how to Enable edge://flags/#edge-windows-credentials-for-http-auth type of behavior as that flag seems to be gone in 84.0.495.2 (or some other relative recent build)? Earlier discussion of w...
Keith Davis
Jan 21, 2021Steel Contributor
Thanks for the update. However, I'm still confused about why this is even changing. Why would Microsoft not want users to be able to use password managers, like LastPass, for their login? How is using Windows Credentials supposed to even replace this?
Fredrik_Freden
Jan 21, 2021Copper Contributor
As far as I understand this is the behavior when using Windows Integreated Authentication. You can use Windows Integrated Authentication to apply single sign on based on your domain credentials and in this case you will not need a password manager.
The problem in my company is that some of our partners have built sites with Windows Integrated Authenticatio. We are not part of their domain and Windows Integrated Authentication will not work because of this. This is when the "bad" credential popup arrives and destroys my day.
So if we get a GPO to adjust this behavior everybody will be happy.
- Fredrik_FredenJan 22, 2021Copper Contributor
I am pretty sure that this solution makes sense in some cases. I don't think Microsoft would implement the feature if it was always useless. But it's good that it will be possible to change the behavior.
- Keith DavisJan 21, 2021Steel Contributor
Again, that makes no sense. Even without this, our single-sign-on works fine for computers on the domain, but for example, when a user that has a domain account connects from a non-domain computer, they get this prompt and instead of being able to use LastPass to autofill, have to manually enter their credentials.