Closed
Bug 1121843
Opened 9 years ago
Closed 9 years ago
FF 35.0 - sso/ntlm-problem - network.negotiate-auth.trusted-uris and network.automatic-ntlm-auth.trusted-uris no longer works
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 1108971
Tracking | Status | |
---|---|---|
firefox35 | --- | affected |
firefox36 | --- | affected |
firefox37 | --- | affected |
firefox38 | --- | affected |
firefox-esr31 | --- | unaffected |
People
(Reporter: burghardt.scholle, Unassigned)
References
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0 Build ID: 20150108202552 Steps to reproduce: After Upgrade FF from 34.x to 35.0 SingleSignOn to our internal dokuwiki-page no longer works. On the "about:config"-page I've checked "network.automatic-ntlm-auth.trusted-uris" and "network.negotiate-auth.trusted-uris". There, my URLs are entered correctly. My System: Windows 7 Pro 64bit Actual results: Despite SingleSignOn a dialog box appears that asks for user name and password. Only after entering the information I get access to our dokuwiki. On another machine with FF 34.x, SSO still works well and I'll be right there on the page. Expected results: I expect that SSO works with Firefox 35 and I will not be prompted for a username and password.
Comment 1•9 years ago
|
||
I have exactly the same problem. FF 34 (before update) worked fine, but after update not. I have to manually enter credentials to access our local intranet pages. SSO does not work. Tested on 2 different servers (Centos 6.6 with Apache 2.2.15 and mod_auth_kerb-5.4 or Centos 5.11 with Apache 2.2.3 and mod_auth_kerb-5.1) Apache said: [Thu Jan 15 08:23:35 2015] [error] [client 10.98.100.10] gss_accept_sec_context() failed: No credentials were supplied, or the credentials were unavailable or inaccessible (, Unknown error)
Updated•9 years ago
|
Comment 2•9 years ago
|
||
Can you try using mozregression to figure out exactly what broke this? using tools: http://mozilla.github.io/mozregression/ OR download builds: http://inbound-archive.pub.build.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-win32/ http://inbound-archive.pub.build.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/
status-firefox35:
--- → affected
status-firefox36:
--- → affected
status-firefox37:
--- → affected
status-firefox38:
--- → affected
status-firefox-esr31:
--- → unaffected
Flags: needinfo?(burghardt.scholle)
Keywords: regressionwindow-wanted
Comment 4•9 years ago
|
||
Brandon, any chance you're able to try alice's suggestion in comment #2 ? It'd really help us if we knew what broke this.
Flags: needinfo?(brandon.stephens)
Updated•9 years ago
|
Summary: FF 35.0 - sso/ntlm-Problem → FF 35.0 - sso/ntlm-problem - network.negotiate-auth.trusted-uris and network.automatic-ntlm-auth.trusted-uris no longer works
I'm just going to check alice's suggestion in comment #2. It takes a time. I'll report.
Flags: needinfo?(burghardt.scholle)
Comment 6•9 years ago
|
||
CAn you just try mozilla-central without changing anything and by changing about:configure dns.ttl-experiment.enabled=false. The first should work and the second should not work. If that is the case than this is the same as bug 1108971. Thank you.
Flags: needinfo?(burghardt.scholle)
I tried the suggestion in https://bugzilla.mozilla.org/show_bug.cgi?id=1121843#c6. But I still have the same problems, as described in my https://bugzilla.mozilla.org/show_bug.cgi?id=1121843#c0. Sorry.
Flags: needinfo?(burghardt.scholle)
Okay, I have a result in the review with mozregression. The nightly build "2014-09-16-03-02-04-mozilla-central/firefox-35.0a1.en-US.win64-x86_64.zip" is still in order. At the nightly build "2014-09-24-03-02-04-mozilla-central/firefox-35.0a1.en-US.win64-x86_64.zip" the problems with SSO occur.
Comment 9•9 years ago
|
||
this will be the same as bug 1108971. https://hg.mozilla.org/mozilla-central/rev/4d21e0728967 Can you please try: http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/dd.mozilla@gmail.com-087449621dfa/try-win32/firefox-37.0a1.en-US.win32.installer.exe Thank you.
Flags: needinfo?(burghardt.scholle)
Reporter | ||
Comment 10•9 years ago
|
||
Great - it works with this version.
Flags: needinfo?(burghardt.scholle)
Comment 11•9 years ago
|
||
Thank you Burghardt!
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Comment 12•9 years ago
|
||
(In reply to Dragana Damjanovic from comment #9) > this will be the same as bug 1108971. > https://hg.mozilla.org/mozilla-central/rev/4d21e0728967 > > Can you please try: > http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/dd.mozilla@gmail. > com-087449621dfa/try-win32/firefox-37.0a1.en-US.win32.installer.exe > > Thank you. Using this build also resolved my issue reported in bug 1121461, comment 3
Flags: needinfo?(brandon.stephens)
Comment 13•9 years ago
|
||
I can confirm this version works for me with Kerberos and aliases, too.
Comment 14•9 years ago
|
||
Yes, I can confirm it too. I'm waiting for fix in official build...
Comment 15•9 years ago
|
||
(In reply to Burghardt from comment #10) > Great - it works with this version. Burghardt, can you just confirm - if you download a build from https://nightly.mozilla.org, this issue is fixed for you, and in a build from http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/dd.mozilla@gmail.com-087449621dfa/try-win32/firefox-37.0a1.en-US.win32.installer.exe it is also fixed, but on 35.0.1 it's *not* fixed? If so, we should probably reopen this...
Flags: needinfo?(burghardt.scholle)
Comment 16•9 years ago
|
||
On my 35.0.1 everything works fine :)
Reporter | ||
Comment 17•9 years ago
|
||
Ok, now it works for me. This morning I performed some tests. I've created a new profile for me and started Firefox. With the new profile SSO and Kerberos works fine. Now it also works on other computers in our network. Thanks a lot.
Flags: needinfo?(burghardt.scholle)
Comment 19•9 years ago
|
||
Per Comment 11 and Comment 18 ,clear "regressionwindow-wanted".
Keywords: regressionwindow-wanted
You need to log in
before you can comment on or make changes to this bug.
Description
•