search

Fox-Alpha / nagioschecker

Automatically exported from code.google.com/p/nagioschecker
0 stars 0 forks source link

Nagios Checker in Firefox fails to work with "Error" without 3rd party cookies enabled #194

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Overview:
I found a problem that was hard to troubleshoot and identify but easy to solve 
once identified.  I'd like to recommend that this be documented or that 
troubleshooting methods (e.g. ask the nagioschecker for error detail) be 
improved.

Summary:
In Firefox, one can disable "third party" cookies, which prevents the 
nagioschecker from accessing a cookie-based authentication protected site.

What steps will reproduce the problem?
0. Prereqs: Have Nagios Checker installed & configured for a Nagios site that 
uses cookie based authentication
1. Disable "Accept third-party cookies" under Firefox's Preferences > Privacy > 
History: Firefox will: [ Use custom settings for history ]

What is the expected output? 

I expect the checker to work (after verifying settings several times) or give 
me a descriptive error.  It is also acceptable to right-click for a menu option 
to view error detail, or under settings enable an error log to be written 
somewhere. 

What do you see instead?

Only "Error" in the add-on tool bar next to the nagios icon.  There is no way I 
was able to find to give more info.  Even telling me, "the nagios status.cgi is 
sending a looping redirect" or some such would be helpful.

What version of the product are you using (Nagios Checker and Nagios)? On what 
operating system?

Nagios:
 Version: 3.4.1 
 OS: Redhat Enterprise Linux 6.3
 Authentication system: cosign (weblogin.org)

Client:
 Browser: Firefox 17.0.1
 OS: Apple OS X 10.7.5
 nagioschecker: 0.16

Repeatable:
 Always (toggled back and forth a few times)

Please provide any additional information below.

If this could be explained somewhere such as a user FAQ or troubleshooting 
site/guide/help pages, or the error provide some detail as to this as the 
problem, that would help greatly.  I had to track this down between wireshark, 
Live HTTP headers and about an hour of debugging.  Arguably not the checker's 
fault being a browser setting but also not very user friendly.

Thanks for considering.

Original issue reported on code.google.com by rewt...@gmail.com on 13 Dec 2012 at 9:43