Bug 821448
Summary: | RFE: Browser config javascript should check to see if sending Referer is enabled | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | David Kovalsky <dkovalsk> | ||||||
Component: | ipa | Assignee: | Rob Crittenden <rcritten> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Namita Soman <nsoman> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 6.2 | CC: | benl, dpal, jgalipea, mkosek, mvarun, pvoborni | ||||||
Target Milestone: | rc | Keywords: | FutureFeature | ||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | ipa-3.0.0-1.el6 | Doc Type: | Enhancement | ||||||
Doc Text: |
Feature: Identity Management Firefox browser configuration script now checks if the browser is configured to sent Referrer header in HTTP requests for Identity Management.
Reason: Firefox browsers which would not have network.http.sendRefererHeader configuration option set to True would fail to connect to Identity Management Web UI even though they run the configuration script.
Result (if any): Configuration script ensures that network.http.sendRefererHeader configuration option is set correctly and the Firefox browser can thus connect to Web UI.
|
Story Points: | --- | ||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2013-02-21 09:13:06 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
David Kovalsky
2012-05-14 14:13:42 UTC
The Apache error log /var/log/httpd/errors may have additional information on the source of the problem. I'm not able to duplicate this. Can you install the Live HTTP headers (or similar) browser plugin to see what is being sent back and forth to the server? This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. Hey Rob, I've installed Live HTTP headers, cleared my cache, logins and cookies and opened the page. Obviously, I've obfusted the hostname and hopefully removed my true login into. There's one 404 in the logs, perhaps relevant? https://my.machine.domain/ipa/ui/develop.js GET /ipa/ui/develop.js HTTP/1.1 Host: my.machine.domain User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 Accept: */* Accept-Language: en-us,cs;q=0.7,en;q=0.3 Accept-Encoding: gzip, deflate Connection: keep-alive HTTP/1.1 404 Not Found Date: Fri, 18 May 2012 15:45:12 GMT Server: Apache Content-Length: 215 Keep-Alive: timeout=5, max=97 Connection: Keep-Alive Content-Type: text/html; charset=iso-8859-1 Full headers attached in a sec. Created attachment 585446 [details]
Full headers
Why is it sending a Basic auth header? Did you enable KrbMethodK5Passwd? Yes I did. I wasn't able to login via negotiate (more info in comment #0). I still can't login in FF, but I can login via password in Chrome as a workaround. I don't know why Firefox wouldn't be sending a Referer header, Basic auth or not. We require a Referer to prevent Cross-Site Request Forgery attacks. Can you try creating a new profile in Firefox to see if that fixes things? Can you go in about:config and check what's the value of Network.http.sendRefererHeader ? Bingo. It's set to 0 (user set, Integer; default is 2). I haven't touch this config, but I seem to recall that when I installed IPA it did some configuration changes to my browser to support negotiate. May it be that it's calling some kind of 'toggle' instead of setting this to 1? (if this is total nonsense, please ignore) We have signed javascript that makes config changes but that is just added a domain to network.negotiate-auth.trusted-uris setting. We do not touch sendRefererHeader. Hmm, in that case I'm not sure what caused this change in Firefox. Is there a way to read the value via JavaScript and guide the user to check the settings? It's really a trivial fix once it'c clear where to look :) Yes, we can use this bug to track that feature. Fixed upstream: * 0948a9f91b3e423df4d06fd13d23b3ec7ccaa921 * 6f4121ccbb83493463a1f05d8a24f46042e8bf1d Created attachment 689031 [details]
in about:confi value is set to 2
verified using ipa-server-3.0.0-22.el6.x86_64 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0528.html |