Sheridan Posted October 3, 2019 Posted October 3, 2019 We've noticed recently that windows authentication isn't working in Chrome. We have a local intranet which uses built in windows authentication and previously it was fine with Chrome. Our policies put the intranet site into Local Intranet and allow for automatic login. However this has now stopped working, and users are given the authentication prompt when opening the site with Chrome. Weirdly it works when you specify the FQDN of the intranet. So: https://intranet doesn't work https://intranet.org.uk does work But in our policies both the short and FQDN names are in the Sites to Zones assignment list as Local Intranet. This does seem to be a fairly recent problem, has anyone else seen this behaviour?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now