Greetings all, CGI access problem

[Clair Johnson]

Hi all,

This is my first post to the list. I've search the archive but didn't find clues to my actual problem.
It's since two years that I'm working with nagios, from the version 2.5 and I very happy and grateful for all the work people have done to this project.

I've developed my own graphical interface to manage nagios core and my authentication. Everything is working great up to last week where I worked to migrate from version 2.9 to version 3.2.

The only problem comes from the CGIs that I use, the statusmap.cgi and avail.cgi. Since I take care by myself of the authentication I don't want the nagios authentication, but when I call the statusmap or avail, I get a dialog box asking me a login and password. I've check the cgi config file and change the use_authentication to 0 but that doesn't change anything, when I call the CGI in my browser I'm still asked for credentials.

My apache configuration hasn't changed and was working in nagios 2.9.

Do you have ideas how to solve my problem, that is to use nagios CGIs without any authentication ?

many thanks for your help

Kind regards
Clair Johnson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20100112/aad36ade/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null