Can't you just do this by playing with the apache and nagios configs?<br>I've done this in the past and it was not really a catch the only thing is that you need<br>2 nagios configurations files: one serving the unauthenticated content with no exec permissions,
<br>one with the authenticated content with the exec permissions (this also means that you need two set<br>of cgi scripts reading different nagios config files).<br><br>Other options is to not use apache native authentication but to create your own apache auth module. This can be done
<br>in perl using mod-perl or mod-python. In this case you setup a proper authentication mechanism under apache with a default<br>guest user account to fallback if no proper auth is provided. This is probably nicer and provides more flexibility but is probably more complicated.
<br>Some examples<br>of apache authentication modules:<br>perl: apache::authcookie (<a href="http://search.cpan.org/~mschout/Apache-AuthCookie-3.10/lib/Apache2/AuthCookie.pm">http://search.cpan.org/~mschout/Apache-AuthCookie-3.10/lib/Apache2/AuthCookie.pm
</a>)<br>python: <a href="http://www.modpython.org/live/current/doc-html/tut-more-complicated.html">http://www.modpython.org/live/current/doc-html/tut-more-complicated.html</a><br>I've done some code on this here: <a href="http://www.barbich.net/websvn/wsvn/nagios/nagios/doc/mod_apache_authentication/?rev=0&sc=0">
http://www.barbich.net/websvn/wsvn/nagios/nagios/doc/mod_apache_authentication/?rev=0&sc=0</a><br><br><br><div><span class="gmail_quote">On 7/29/07, <b class="gmail_sendername">Paul Dugas</b> <<a href="mailto:paul@dugas.cc">
paul@dugas.cc</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Been fiddling with this for a while now and am stumped. I figure I'm
<br>not the first to want this so before I get a brain cramp I'll ask.<br><br>I run a couple Nagios server on internal networks and I want internal<br>users to get read access without having to log in. I want a select
<br>number of users to be able to login and get higher level access. I've<br>been trying to get the HTTP interface default to the guest account and<br>the HTTPS interface to require a login. My admins and I would use the
<br>HTTPS interface while our customers would use the standard HTTP<br>interface.<br><br>Anybody got something like this going? Perhaps something else that<br>would accomplish the same? Any info would be appreciated.<br>
<br>pd<br>--<br>Paul Dugas, Computer Engineer Dugas Enterprises, LLC<br><a href="mailto:paul@dugas.cc">paul@dugas.cc</a> phone: 404-932-1355 522 Black Canyon Park<br><a href="http://dugas.cc">http://dugas.cc
</a> fax: 866-751-6494 Canton, GA 30114 USA<br>--<br>This e-mail and any attachments are confidential. If you receive<br>this message in error or are not the intended recipient, you should<br>not retain, distribute, disclose or use any of this information and
<br>you should destroy the e-mail and any attachments or copies.<br><br>-------------------------------------------------------------------------<br>This SF.net email is sponsored by: Splunk Inc.<br>Still grepping through log files to find problems? Stop.
<br>Now Search log events and configuration files using AJAX and a browser.<br>Download your FREE copy of Splunk now >> <a href="http://get.splunk.com/">http://get.splunk.com/</a><br>_______________________________________________
<br>Nagios-users mailing list<br><a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br><a href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users
</a><br>::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<br>::: Messages without supporting info will risk being sent to /dev/null<br><br></blockquote></div><br>