Chrome not able to pass the Authorization header as NTLM authentication code(Hosted In IIS). Prompts AuthenticationRSS

1 reply

Last post Feb 08, 2017 08:15 AM by lextm

  • Chrome not able to pass the Authorization header as NTLM authentication code(Hosted In IIS). Prom...

    Feb 08, 2017 06:33 AM|boopesh|LINK

    We are using MVC application with AngularJS which is a Windows authentication based application(NTLM) hosted in IIS. When I browse my application in IE, it works fine. IE passed the Authorization header as NTLM authentication code. and it works fine in Firefox as well.

    But when I try to open the application in chrome, it keeps prompting for Authentication. I confirmed that in Fiddler as well. In request header, authorization header was passed as bearer token authentication type. Can this be the cause of the issue? If Yes, is there any other way to overcome this.

    I was not able to call any WebApi from angularJS http post from chrome. Is there any way to avoid that? is there any specific code that has to be added in WebAPIConfig.cs file to handle NTLM Authentication?

  • Re: Chrome not able to pass the Authorization header as NTLM authentication code(Hosted In IIS)....

    Feb 08, 2017 08:15 AM|lextm|LINK

    Clearly it is a Chrome issue, and it does not work quite well with NTLM. Let Google know and hope they can fix that for you.

    Lex Li
    https://lextudio.com
    ---------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights.