Nagios v3 & WAP

[Hart, Harry M. CTR USJFCOM SUPPORT.SUPPORT JTC-I]

Are we playing stump the dummy? What is WAP? 


Harry M. Hart Systems integrator
(757) 203-7422
DSN 668-7422
Harry.Hart at intel.jwfc.jfcom.smil.mil
Harry.Hart at jwfc.ic.gov

-----Original Message-----
From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Robert
Small
Sent: Monday, July 14, 2008 12:35 PM
To: Nagios Users Mailinglist
Subject: [Nagios-users] Nagios v3 & WAP

I recently upgraded from Nagios2 to version3, and it's running
beautifully.  All except for the WAP interface.  I've searched the web,
and the archives and haven't found anything that might help.

When my users go to the wap interface (which worked GREAT under v2) and
try to acknowledge a problem (either a host or a service), they get:

Error: You're not authorized to commit that command!

I've made sure that they all have access to:

Authorization Requirements: 
If you are authorized for system information you can view Nagios process
information. 
If you are authorized for all hosts you can view status data for all
hosts and services. 
If you are authorized for all services you can view status data for all
services. 

And they are authenticating.

If you are an authenticated contact you can view status data for all
hosts and services for which you are a contact. 

Any ideas and help would be appreicated.

Thanks!

Robert 

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Nagios-users mailing list
Nagios-users at 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