Thanks Marc
On Sat, May 23, 2009 at 9:49 PM, Marc Powell m...@ena.com wrote:
On May 23, 2009, at 8:11 AM, Ayotunde Itayemi wrote:
Hi,
Thanks for the response. Each authentication method works OK alone,
but I need to allow regular Windows AD users “read-only” access to
the Nagios web
Hi All,
I would like to use both NTLM authentication and htpasswd authentication
to grant access to the NAGIOS web interface. If possible, authenticate
against Windows AD first, and if not successful, authenticate against
the apache htpasswd file (possibly use the htpasswd file like a
Hi Tunde,
I have never tried this before but I will suggest you try your auth systems
one at a time to know they are working before implementing them.
Nagios uses apache http authentication by default so you should not have any
issues with this. Or maybe I am missing something, please correct if
both NTLM and htpasswd file
authentication for NAGIOS web interface
Hi Tunde,
I have never tried this before but I will suggest you try your auth
systems one at a time to know they are working before implementing them.
Nagios uses apache http authentication by default so you should not have
-users] Using both NTLM and htpasswd file
authentication for NAGIOS web interface
You want to send this to the nagios developer mailing list. Seems you
are spoiling your users - why can't they all authenticate from one
source - apache?
Regards,
Alex
On Sat, May 23, 2009 at 1:11 PM, Ayotunde Itayemi
and htpasswd file
authentication for NAGIOS web interface
Hi Tunde,
I have never tried this before but I will suggest you try your auth systems
one at a time to know they are working before implementing them.
Nagios uses apache http authentication by default so you should not have
any issues
On May 23, 2009, at 8:31 AM, Alex Dehaini wrote:
You want to send this to the nagios developer mailing list. Seems
you are spoiling your users - why can't they all authenticate from
one source - apache?
This has nothing to do with nagios-devel. Nagios does not know or care
about any
