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, we would pass their > username > over to Nagios via URL querystring or hidden form value, etc (not > going for > maximum security). On the Nagios server we would use PHP to > populate the > REMOTE_USER Apache ENV variable with the passed username so that > Nagios can > compare that to the contacts and provide them with their applicable > views.
You can pass htaccess authentication as part of the URL but I don't know if it's sticky for links accessed from that page -- http://username:[EMAIL PROTECTED] I'm not aware of other methods to transparently pass it but they may exist. htaccess has been around for quite a long time. -- Marc ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Nagios-users mailing list Nagios-users@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
