New issue
Advanced search Search tips

Issue 760689 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

NTLM Auth issue

Reported by pankaj.c...@gmail.com, Aug 30 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36

Steps to reproduce the problem:
1. Enter DOMAIN/useraccount and password NTLM fails
2. 
3. 

What is the expected behavior?

What went wrong?
We have deployed Chrome 60 on mac machines and found that ntlm is not working.
We have tested the same on chrome 58 and it is working fine.Also we have tested the same ntlm authentication for the same application and it is working fine on chrome 41,53 versions too. 
While using our application after browsing URL, NTLM authentication form pops up, where we are entering <Domainname>/useraccount and password. After entering it immediately shows 403 forbidden error though we are entering correct one. We have tested this with 58 version of chrome also and it works fine. 
We have tested 60 stable and 61b and on these 2 versions we are getting ntlm issue.

Could you please look into this issue?

Did this work before? N/A 

Chrome version: 60.0.3112.113  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 

Comment 1 by mmenke@chromium.org, Aug 30 2017

Cc: asanka@chromium.org
Components: Internals>Network>Auth
Could you please provide a net-export log?  Instructions:  https://dev.chromium.org/for-testers/providing-network-details (Note that the log will include URLs, but not cookies or any NTLM credentials)

Comment 2 by mmenke@chromium.org, Aug 30 2017

Labels: Needs-Feedback
@pankaj...: Could you provide the net log as requested in c#1?  We need your help to make progress on this issue.

Comment 4 by rch@chromium.org, Sep 25 2017

Status: WontFix (was: Unconfirmed)
It's been almost a month without hearing anything back so I'm going to close this bug. Please reopen if you get a net-internals trace.

Sign in to add a comment