I have achieved something like you describe with a Reverse Proxy SSO
called Vulture NG (http://vulture.open-source.fr/wiki/). It works
really well when you need to authenticate on differents nagios servers
(like in a distributed setup).
Maybe this can help you
Olivier Jan
Marc Powell <[EM
On Oct 29, 2008, at 10:37 AM, Phillips, Dustin B (DBphillips) wrote:
>
> Thanks for the replies.
>
> Ultimately what we would like to do is authenticate the user via
> another
> website that we already use as a "single sign-on" portal for other web
> applications. Once they're logged in there,
> applications. Once they're logged in there, we would pass their username
> over to Nagios via URL querystring or hidden form value, etc (not going for
> maximum security).
Indeed not, anyone who wants can pretend to be anyone else. Still, if it's an
internal intranet, and you capture the IP
Thanks for the replies.
Ultimately what we would like to do is authenticate the user via another
website that we already use as a "single sign-on" portal for other web
applications. Once they're logged in there, we would pass their username
over to Nagios via URL querystring or hidden form value
On Tue, 28 Oct 2008, Allan Clark wrote:
> Hi Dustin;
>
> Be reminded that if you use this method (and it's what I used) then you need
> to remember to use a wildcard (*) in your /etc/nagios/cgi.cfg to give all who
> can see the CGI access via Apache the access to do it. Otherwise, Apache
> ve
Exactly. You want to make sure a contact is setup and is assigned to
the appropriate objects. The contact name should make the name
authenticated by apache.
Taylor
On Tue, Oct 28, 2008 at 12:50 PM, Marc Powell <[EMAIL PROTECTED]> wrote:
>
> On Oct 28, 2008, at 2:35 PM, Allan Clark wrote:
>
>> H
On Oct 28, 2008, at 2:35 PM, Allan Clark wrote:
> Hi Dustin;
>
> Be reminded that if you use this method (and it's what I used) then
> you need to remember to use a wildcard (*) in your /etc/nagios/
> cgi.cfg to give all who can see the CGI access via Apache the access
> to do it. Otherwise
On Oct 28, 2008, at 2:08 PM, Phillips, Dustin B (DBphillips) wrote:
> Sorry if this has already been asked but I’m new to the list.
>
> Question: Is there an add-on or other method for enabling more
> advanced authentication for Nagios or is htaccess the only method?
> I’m thinking somethin
On Tue, Oct 28, 2008 at 3:08 PM, Phillips, Dustin B (DBphillips)
<[EMAIL PROTECTED]> wrote:
> Question: Is there an add-on or other method for enabling more advanced
> authentication for Nagios or is htaccess the only method? I'm thinking
> something more like a MySQL database or LDAP, etc.
Yo
Hi Dustin;
Be reminded that if you use this method (and it's what I used) then you need
to remember to use a wildcard (*) in your /etc/nagios/cgi.cfg to give all
who can see the CGI access via Apache the access to do it. Otherwise,
Apache verifies their user/pass, but the Nagios CGI denies them.
You can use any type of authentication that apache supports. For both
of your suggestions, you should look at:
LDAP Authentication
http://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html
Database backend Authentication
http://httpd.apache.org/docs/2.2/mod/mod_authn_dbd.html
Taylor
On Tue, Oc
Hi Dustin,
As the htaccess authentication is provided by Apache, you can certainly
use any authentication Apache supports (LDAP, SQL etc.) See the
following Apache manual pages:
http://httpd.apache.org/docs/2.2/howto/auth.html - htaccess
authentication howto
http://httpd.apache.org/docs/2.2/mo
Sorry if this has already been asked but I¹m new to the list.
Question: Is there an add-on or other method for enabling more advanced
authentication for Nagios or is htaccess the only method? I¹m thinking
something more like a MySQL database or LDAP, etc.
Thanks,
Dustin
E-MAIL CONFIDENTIALI
13 matches
Mail list logo
