MicrosoftMatthew_Palko We have a number of Legacy Web Applications (ASP.NET Framewokr 4.8) on which we use Windows Authentication (Negotiate).
On Windows 11 24H2 I have tried to create a blank application as above by selecting Windows Authentication as the Authentication provider, and with only negotiate running in IIS Express (removed NTLM from the applicationhost.config file).
The computer is connected to a local domain (DC is Windows 2022 Server Std).
Whenever I run this application locally (Starting from Visual Studio) - As far as I can tell by using W******* (Why is that not permitted? o.O) it ends up negotiating it to NTLM. Given these plans of phasing out NTLM entirely.
- I supose that this should use Kerberos instead?
- How far along is Microsoft on that part?
- or Should that actually already work?
I tried going through the same with a fresh ASP.NET (Core) 9 application, but I could not as easily find out what it ended up with there. But I am somewhat confident that this also ends up using NTLM as the whole reason I am investigating this is that our Company is in the process of moving to Entra Joined Windows 11 PC's where NTLM is blocked (I am told) and we can't get our development environments to work for these projects.
