<div dir="ltr">Keven, <br><br>Yes when nagios is doing nothing it sits exactly for 10 mins i managed to make it 30 mins by changing the LDAPCacheTTL parameter in httpd.conf but it only gave me time upto 30 mins then started giving authentication errors because it was checking against the cached password. <br>
<br>we are using RSA through LDAP for the majority of our services to have a secure ad centralized user DB, we have a group of users with different permissions thats why the default user wouldn't work in our case.<br>
<br>i was hoping to find the parameter that sets the 10min idle timeout for the browser/nagios/ldap combo<br><br><br clear="all">Best Regards<br>--<br>Mohammed Al-Kout<br><br><br><br>
<br><br><div class="gmail_quote">On Sat, Jan 24, 2009 at 14:53, Kevin Keane <span dir="ltr"><<a href="mailto:subscription@kkeane.com">subscription@kkeane.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If the RSA password really changes every minute, your Web browser should ask for a new password every minute with the next HTTP request. If Nagios simply sits there and you don't do anything, I believe it refreshes every five to ten minutes. So that is when the browser would ask for the new password. If you are actually working with it and clicking on links, then it would probably ask for a password earlier.<br>
<br>
BTW, could you post this back to the mailing list rather than me personally? Other people may have great ideas on it, too, and this type of discussion should also be archived.<br>
<br>
What might help here is something along the lines of Kerberos, but I believe Apache does not support it, at least not out of the box.<br>
<br>
The other possibility is to have some kind of "front end" that handles authentication and then forwards the HTTP requests to Nagios. In Nagios, you could then use the default-user to allow access for anyone (you wouldn't be able to restrict access by group or so, though).<br>
<br>
Personally, I think that for Nagios purposes, you should ditch RSA and go back to a local password file for nagios. I suspect using RSA with Nagios actually reduces rather than increases the security. This is because an attacker could potentially see many different passwords, and use that to deduct information about the sequence of RSA keys and possibly in the end predict the next one. RSA is pretty strong overall, so this is not a huge risk, but something to keep in mind.<br>
<br>
Mohammed Al-Kout wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Keven,<br>
<br><div class="Ih2E3d">
The rsa password changes every 1 min, the nagios session timeouts ( i.e requires re authentication ) every 10 mins, all i need is is there a way to change this value to stay longer than 10 mins ? like 2-3 hours for example.<br>
<br>
Best Regards<br>
--<br>
Mohammed Al-Kout<br>
<br>
<br>
<br>
<br>
<br></div><div class="Ih2E3d">
On Sat, Jan 24, 2009 at 11:57, Kevin Keane <<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a> <mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>>> wrote:<br>
<br>
Of course you wouldn't get it with the local passwd file, because<br>
that password never changes. It's not the LDAP Cache settings, but<br>
the fact that your RSA passwords themselves are changing<br>
frequently - presumably every ten minutes - as you said earlier.<br>
<br>
Mohammed Al-Kout wrote:<br>
<br>
Keven,<br>
<br>
we didn't get the reauthenticate window when we had the local<br>
passwd file once we enabled ldap authentication its repopping<br>
at exactly 10 mins it has something to do with the LDAP Cache<br>
settings.<br>
<br>
Best Regards<br>
--<br>
Mohammed Al-Kout<br>
<br>
<br>
<br>
<br>
<br>
On Fri, Jan 23, 2009 at 15:32, Kevin Keane<br>
<<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a> <mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>><br></div><div class="Ih2E3d">
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>>>> wrote:<br>
<br></div><div class="Ih2E3d">
There is no "idle timeout" when using HTTP authentication,<br>
because<br>
there are no sessions involved that would be idle.<br>
<br>
Each request stands on its own, and is separately<br>
authenticated.<br>
<br>
Mohammed Al-Kout wrote:<br>
<br>
What about the idle timeout ?<br>
<br>
Best Regards<br>
--<br>
Mohammed Al-Kout<br>
<br>
<br>
<br>
<br>
<br>
On Thu, Jan 22, 2009 at 09:49, Kevin Keane<br>
<<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a> <mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>>><br></div><div>
<div></div><div class="Wj3C7c">
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>>>>> wrote:<br>
<br>
No. It has nothing to do with time. The popup will<br>
come up<br>
every<br>
time the RSA password changes. So the only solution<br>
is to<br>
reduce<br>
how often the password changes.<br>
<br>
Mohammed Al-Kout wrote:<br>
<br>
Keven,<br>
<br>
is it possible to give the browser certain<br>
parameters to<br>
increase this time ? ( we are using Firefox )<br>
<br>
Best Regards<br>
--<br>
Mohammed Al-Kout<br>
<br>
<br>
<br>
<br>
<br>
On Wed, Jan 21, 2009 at 17:19, Kevin Keane<br>
<<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>>><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a> <mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>>>><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>>><br>
<br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a><br>
<mailto:<a href="mailto:subscription@kkeane.com" target="_blank">subscription@kkeane.com</a>>>>>> wrote:<br>
<br>
There is no such thing as a "session" in<br>
Nagios. It<br>
simply<br>
uses plain<br>
HTTP authentication. That means that the user<br>
name and<br>
password is<br>
sent<br>
with every single HTTP request; request are<br>
not tied<br>
together the way<br>
you might be used to from online banking<br>
sites and<br>
the like.<br>
<br>
What you are observing could be due to a<br>
couple of<br>
different factors,<br>
but it is almost certainly neither LDAP,<br>
Apache nor<br>
Nagios,<br>
but rather<br>
the Web browser.<br>
<br>
- The most likely cause: you say that the RSA<br>
passwords change<br>
frequently. When the RSA password changes, the<br>
browser has<br>
no way of<br>
knowing that, and will continue to send the old<br>
password.<br>
This is<br>
rejected, and the browser then pops up the<br>
login dialog.<br>
<br>
- The browser may for some reason think that<br>
it is<br>
connecting to a<br>
different server, where the user name and<br>
password<br>
are no<br>
longer<br>
valid.<br>
<br>
- The browser may for some reason actually forget<br>
the user<br>
name and<br>
password.<br>
<br>
Mohammed Al-Kout wrote:<br>
> Warner,<br>
><br>
> the session seems to be expiring after (<br>
10-20) and<br>
nagios asks for<br>
> reauthentication, ( we are using RSA passwords<br>
that change<br>
frequently<br>
> so the LDAPCAche does not apply in our case<br>
) are<br>
you using<br>
> mod_auth_ldap ?<br>
> what are the parameters you use in the<br>
httpd.conf for<br>
LDAP Cache<br>
settings<br>
><br>
> Best Regards<br>
> --<br>
> Mohammed Al-Kout<br>
><br>
><br>
><br>
><br>
><br>
> On Wed, Jan 21, 2009 at 16:22, Werner Flamme<br>
<<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>> <mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>>><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>> <mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>>>><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>>> <mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>>>>><br>
> <mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a> <mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>>><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>>>> <mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a> <mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>>><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a><br>
<mailto:<a href="mailto:werner.flamme@ufz.de" target="_blank">werner.flamme@ufz.de</a>>>>>>> wrote:<br>
><br>
> Mohammed Al-Kout [21.01.2009 14:00]:<br>
> > Hello,<br>
> ><br>
> > i'm running Nagios 3.0.1 on Apache 2.0.52<br>
its been<br>
running<br>
on a<br>
> local<br>
> > userfile for sometime, recently i<br>
switched<br>
to LDAP<br>
> authentication with<br>
> > mod_auth_ldap its working fine, the<br>
problem<br>
is i'm<br>
getting the<br>
> > authentication popup every 10-20 mins, is<br>
there a<br>
way to stop<br>
> this or set a<br>
> > longer interval ? i'm not sure what<br>
is causing<br>
this popup to<br>
> reappear (<br>
> > LDAP , Apache or Nagios ) if anyone<br>
has an<br>
idea please<br>
lemme know<br>
><br>
> Neither of them. We use LDAP auth for<br>
years, and<br>
there are<br>
no such<br>
> popups.<br>
><br>
> Regards,<br>
> Werner<br>
><br>
<br>
<br>
<br>
-- Kevin Keane<br>
Owner<br>
The NetTech<br>
Find the Uncommon: Expert Solutions for a Network You Never<br>
Have<br>
to Think About<br>
<br>
Office: 866-642-7116<br>
<a href="http://www.4nettech.com" target="_blank">http://www.4nettech.com</a><br>
<br>
This e-mail and attachments, if any, may contain confidential<br>
and/or proprietary information. Please be advised that the<br>
unauthorized use or disclosure of the information is strictly<br>
prohibited. The information herein is intended only for use<br>
by the<br>
intended recipient(s) named above. If you have received this<br>
transmission in error, please notify the sender immediately and<br>
permanently delete the e-mail and any copies, printouts or<br>
attachments thereof.<br>
<br>
<br>
<br>
<br>
-- Kevin Keane<br>
Owner<br>
The NetTech<br>
Find the Uncommon: Expert Solutions for a Network You Never Have<br>
to Think About<br>
<br>
Office: 866-642-7116<br>
<a href="http://www.4nettech.com" target="_blank">http://www.4nettech.com</a><br>
<br>
This e-mail and attachments, if any, may contain confidential<br>
and/or proprietary information. Please be advised that the<br>
unauthorized use or disclosure of the information is strictly<br>
prohibited. The information herein is intended only for use by the<br>
intended recipient(s) named above. If you have received this<br>
transmission in error, please notify the sender immediately and<br>
permanently delete the e-mail and any copies, printouts or<br>
attachments thereof.<br>
<br>
<br>
</div></div></blockquote><div><div></div><div class="Wj3C7c">
<br>
<br>
-- <br>
Kevin Keane<br>
Owner<br>
The NetTech<br>
Find the Uncommon: Expert Solutions for a Network You Never Have to Think About<br>
<br>
Office: 866-642-7116<br>
<a href="http://www.4nettech.com" target="_blank">http://www.4nettech.com</a><br>
<br>
This e-mail and attachments, if any, may contain confidential and/or proprietary information. Please be advised that the unauthorized use or disclosure of the information is strictly prohibited. The information herein is intended only for use by the intended recipient(s) named above. If you have received this transmission in error, please notify the sender immediately and permanently delete the e-mail and any copies, printouts or attachments thereof.<br>
<br>
</div></div></blockquote></div><br></div>