PaulBendall
commented
3 years ago Same issue as reported by @JakeMoe, although running the browser in same context as logged on user.
Gateway Version: 1.3.2105.24004 Server version: Windows 2019 Standard (Core) 1809 (10.0.17763) Client version: Windows 10 21H1 build 19043.1165 Microsoft Edge version: 93.0.961.38
If it works with just computer name and not FQDN does that not infer NTLM works and Kerberos fails?
Gateway Version: 1.3.2105.24004 Server version: Windows 2019 Standard 1809 Client version: Windows 10 2004 build 19041.1110 Microsoft Edge version: 92.0.902.67 (not working) Google Chrome version: 92.0.4515.131 (working) Mozilla Firefox version: v90.0.2 (working)
To Reproduce Steps to reproduce the behavior:
Expected behavior A login prompt when accessing via FQDN
Screenshots & Additional context I have a WAC installed on Server 2019 that I'm trying to connect to from my Windows 10 client. It's using a cert from our domain CA issued to the server name, with SANs of servername, servername.ADdomain.com, and wac.DNSdomain.com. If I try to log in via Microsoft Edge using the either of the FQDNs, I get the error above. If I log in using https://servername (no domain), it works. However, I can't sign in to Azure as the redirect URL doesn't match.
All three names work in Chrome and Firefox.
I should mention that for all three browsers, I am logged into my computer as my user account, and use "Run as different user" to start the browser as my admin account; this is the browser I use for O365 admin, Azure admin, and other admin tasks. I'm assuming there's some integrated Windows auth getting in the way in Edge? If I start Edge normally, I receive a logon prompt, but it doesn't seem to work in the browser started with "Run as different user".