Hi,

Since upgrading, my authenticated openid users can no longer see Host
or Service status details;

"It appears as though you do not have permission to view information
for any of the services you requested..."

I am running similar configuration options as previously, cgi
authentication is on;

use_authentication=1
authorized_for_system_information=*
authorized_for_configuration_information=*
authorized_for_system_commands=*
authorized_for_all_services=*
authorized_for_all_hosts=*
authorized_for_all_service_commands=*
authorized_for_all_host_commands=*

I've  manually killed the old processes to check for hangers-on, and
these users are explicitly listed as "contact" objects in contacts.cfg
like so;

define contact {
  use          default-contact
  contact_name 
https://www.google.com/accounts/o8/id?id=AItOawnTVy0slAaQLXPai61aW4hU9UL2jwdmyxX

}

The users show as logged in in the portal;

"Current Network Status
Last Updated: Sun Jan 13 18:55:06 PST 2013
Updated every 90 seconds
NagiosĀ® Coreā„¢ 3.4.4 - www.nagios.org
Logged in as 
https://www.google.com/accounts/o8/id?id=AItOawnTVy0slAaQLXPai61aW4hU9Ul2jwdmyxU";

and seem to have access to the other configurable levels such as
system_information, and configuration_information

Any suggestions?

Cheers,
Tom

ps. so the log file is not very informative, and the cgi do not seem
to be logged to nagios.log (thought they are logged in httpd.log)

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
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

Reply via email to