New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 801084 link

Starred by 16 users
Status: Fixed
Owner:
zentaro@chromium.org
Closed: Nov 12
Cc:
pastarmovj@chromium.org
█ blumberg@chromium.org
isandrk@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug


Show other hotlists

Hotlists containing this issue:
Hotlist-1
Hotlist-2
Hotlist-1


Sign in to add a comment

Chrome Mobile Policy: describe your issue

Reported by johsonc...@gmail.com, Jan 11 2018 
Chrome Version       : <Copy from: 'chrome beta 64.0.3282.73'>
URLs (if applicable) : internal network
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:OK
    Firefox:OK
       Edge:OK

What steps will reproduce the problem?
(1)visit a website using windows authentication NTLM
(2)enter account & pass in Pop-up prompt and make sure the account&password are correct.
(3)click login button

What is the expected result?
Successful authentication。

What happens instead?
authentication failed,and pop-up prompt again.

Please provide any additional information below. Attach a screenshot if
possible.

Comment 1 by dtapu...@chromium.org, Jan 23 2018

Components: Enterprise

Comment 2 by isandrk@chromium.org, Jan 24 2018

Cc: isandrk@chromium.org
Owner: pastarmovj@chromium.org

Comment 3 by pastarmovj@chromium.org, Jan 26 2018

Cc: pastarmovj@chromium.org
Owner: blumberg@chromium.org
Hey Matt, can you please forward this bug to whoever was working on NTLM because I don't remember anymore but I know there were some changes there recently.

Comment 4 by blumberg@chromium.org, Jan 26 2018

Cc: blumberg@chromium.org dskaram@chromium.org
Owner: zentaro@chromium.org

Comment 5 by zentaro@chromium.org, Jan 31 2018 

Assuming that the other browsers work in their default configuration, that must mean the server is using NTLMv2.

Chrome 64 only supports NTLMv2 by enabling a flag. If this is the reason this isn't a regression, all prior Chrome versions on non-Windows platforms also did not support NTLM. Also note that all browsers (including Chrome) use a system library on Windows and support NTLMv2.

In M64 you can enable NTLMv2 with this flag. chrome://flags/#enable-ntlm-v2 

Can you verify if this fixes the issue?

Comment 6 by zentaro@chromium.org, Jan 31 2018 

In #5 this meant to say "all prior Chrome versions on non-Windows platforms also did not support NTLMv2".

Comment 7 by johsonc...@gmail.com, Mar 13 2018 

Sorry for coming back late.

I change the flag to enable. (chrome://flags/#enable-ntlm-v2 ) 
and I tested in my phone ,it's work. But the flag seems to only be used in the beta version.

iOS version : 65.0.3325112 failed (cannot find the item named enable-ntlm-v2)
Android version: 64.0.3282.73  success.

Comment 8 Deleted

Comment 9 Deleted

Comment 10 Deleted

Comment 11 Deleted

Comment 12 by hyunjoon...@gvcspa.org, Sep 4 

HELLO? What are we doing here?

Comment 13 by zentaro@chromium.org, Nov 12

Cc: -dskaram@chromium.org
This should already be resolved.

NTLMv2 has been enabled by default for many releases now.

Comment 14 by zentaro@chromium.org, Nov 12

Status: Fixed (was: Unconfirmed)
►

Sign in to add a comment