NTLM Authorization
Reported by
niveshpa...@gmail.com,
Oct 13 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Example URL: Steps to reproduce the problem: 1.Enter DOMAIN/user account 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. Did this work before? N/A Chrome version: 61.0.3163.100 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: The application is an intranet application which needs to authenticate its user based on the windows authentication. But when user tries to authenticate it receives ERR_UNEXPECTED 401 in the response. Once we refresh the page it allows the authentication to work.
,
Oct 13 2017
,
Oct 13 2017
The log you've attached indicates that the authentication handshake succeeded. Also I don't see any HTTP 403 responses. c#0 mentions two issues: * One where a 403 forbidden page is displayed after authentication. * One where a 401 page is displayed when accessing a protected page, but works correctly after refresh (?) Could you clarify which one you saw when you were collecting the log?
,
Oct 13 2017
While generating the logs I have got first 401 error in the console and page is still in the middle of loading. If later I refresh the page it loads all the data.
,
Nov 17 2017
,
Nov 17 2017
I have already updated the defect with the comments. Please let me know if you need any further information to be able to resolve the issue.
,
Mar 15 2018
The log contains a 401 challenge that succeeds with no delay on Chrome's part. There's also no 403 responses as mentioned in #3. I'm afraid given the log there's no anomaly to analyze. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by niveshpa...@gmail.com
, Oct 13 20172.1 MB
2.1 MB View Download