title: Windows authentication not working properly on Chrome
body: <p>So this is kind of odd.</p>
  
  <p>My scenario:</p>
  
  <ul>
  <li><p>Web server running IIS, hosting asp.net applications</p></li>
  <li><p>SQL server</p></li>
  </ul>
  
  <p>As they are on separate servers, I had to set up kerberos delegation. I have got this working.
  So a user goes to asp.net application hosted on the web server, and it authenticates them to the SQL server.</p>
  
  <p>On one of my web apps, when they go to it in Chrome, I get the error page with SQL authentication failed due to Anonymous user. If they go to the same app in IE, it works correctly.</p>
  
  <p>Here is the really odd part - if they then go to it again in Chrome, it works!</p>
  
  <p>So I guess there is some inconsistency in how Chrome authenticates.
  I found someone suggesting it might be to do with the IIS negotiation providers, but as it needs kerberos delegation I have to have "Negotiate" as the first option or it fails completely.</p>
  
  <p>I guess I could just tell users they have to use IE, but I would prefer to get it to work in Chrome.</p>
  
  <p>Any thoughts?</p>
  
  <p>(Possibly similar to <a href="https://stackoverflow.com/questions/28768726/kerberos-not-working-with-chrome">Kerberos not working with Chrome</a> but it's all on intranet zone, so don't think there's anything to whitelist)</p>