Description of problem: After yum update firefox and midori fail to authenticate to IIS sites. Chrome works OK. Must be some lib used by both ff and midori (update component accordingly). I tried also deleting .mozilla and creating a fresh user (su- to it) - nothing helps. Version-Release number of selected component (if applicable): ff 30 (fc 20 updated fully on 17.6.2014), ask for addl component versions How reproducible: Log in to a IIS based site. You will get just 401 or the site won't work (blank page). On one site I get: You are not authorized to view this page You do not have permission to view this directory or page using the credentials that you supplied because your Web browser is sending a WWW-Authenticate header field that the Web server is not configured to accept. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Kaie, any idea here?
I need more details. Can you point us to a public URL where we can see the problem? Is this a password-popup authentication (basic auth)? Is https involved?
All the sites I tried use windows authentication. A pop-up opens asking for a username/password. The username I enter is in the format: DOMAIN\me I don't know of any public systems that use this auth. However as said all IIS based sites in my company stopped working. You can try some SharePoint sites if you have any. What happens is that the pop-up does not appear (as it does from other machines (linux/windows) and fc20 google-chrome). No https. Is there some component used by both ff and midori that handles the auth? Was it updated recently?
By comparing ff and chrome, I found that both get first a: "HTTP/1.1 401 Unauthorized" ... ff stops there, but chrome continues with: GET / HTTP/1.1 Host: xxxxxxxxx Connection: keep-alive Authorization: NTLM
Thanks for the details. I see that upstream Firefox has disabled support for insecure NTLMv1 in Firefox 30. See https://bugzilla.mozilla.org/show_bug.cgi?id=828183 I also see, they have introduced a pref for users who really really want to continue using the insecure mechanism (see: https://bugzilla.mozilla.org/show_bug.cgi?id=999306 ) I found this page with info: http://www.janbambas.cz/ntlm-v1-and-firefox/ Use at your own risk.
OK, so by setting (at my own risk): network.negotiate-auth.allow-insecure-ntlm-v1 in about:config to true. FF 30 works. I get the credentials dialog as before and I can access the site. What about midori? Should I open a new bug?
(In reply to Samo Dadela from comment #6) > What about midori? Should I open a new bug? Yes please.
Bug 1110734 - midori fails to login to IIS sites after update https://bugzilla.redhat.com/show_bug.cgi?id=1110734 Thanks.