Closed
Bug 1008855
Opened 11 years ago
Closed 6 years ago
Authentication via NTLM fails in TB30 beta, did work in TB29 beta bc. NTLM v1 is disabled by default on 30
Categories
(MailNews Core :: Networking, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: iannbugzilla, Unassigned)
References
Details
(Keywords: regression, relnote, Whiteboard: [relnote tb31])
Just updated to TB 30 beta 1 (application build ID 20140509030228) and authentication to my exchange IMAP account is now being refused.
Prior to the update I was using TB 29 beta which worked fine.
STR
1/ Start with TB 29 beta and an exchange IMAP account authenticating via NTLM
2/ Confirm you can access successfully authenticate via NTLM
3/ Allow TB to upgrade to TB 30 beta
4/ Try to authenticate via NTLM
Expected Result
1/ Authentication works and you can read your emails
Actual Result
1/ Prompted to retry, enter new password or cancel
2/ Cannot read email unless I change authentication method to "Normal Password"
Comment 1•11 years ago
|
||
Hmm, http://www.janbambas.cz/ntlm-v1-and-firefox/ - NTLM v1 is disabled by default on 30.
So does setting network.negotiate-auth.allow-insecure-ntlm-v1 true work?
(In reply to Magnus Melin from comment #1)
> Hmm, http://www.janbambas.cz/ntlm-v1-and-firefox/ - NTLM v1 is disabled by
> default on 30.
>
> So does setting network.negotiate-auth.allow-insecure-ntlm-v1 true work?
Yes, indeed it does. As far as I can see the only two authentication methods that work with Exchange via IMAP are "Normal Password" and "NTLM". I do use SSL/TLS but I didn't think that securely transmits a normal password.
Comment 3•11 years ago
|
||
I suppose we should just relnote this for 31...
Keywords: relnote
Summary: Authentication via NTLM fails in TB30 beta, did work in TB29 beta → Authentication via NTLM fails in TB30 beta, did work in TB29 beta bc. NTLM v1 is disabled by default on 30
Whiteboard: [relnote tb31]
Comment 6•6 years ago
|
||
IIUC this is a complaint that TB default doesn't support NTML v1 auth by default. But this is intentional. So closing as wontfix.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Flags: needinfo?(mkmelin+mozilla)
You need to log in
before you can comment on or make changes to this bug.
Description
•