After update, to R 2.5, and restarting of the server, I get on all checks following errormessage, btw. i'm logged in as nagiosadmin
You are not authorized to access this feature. Contact your Nagios XI administrator for more information, or to obtain access to this feature.
any idea
Regards Andy
authorization Problem after update to 2.5
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: authorization Problem after update to 2.5
Can you attach or copy your cgi.cfg for us to take a look at? If not, is the nagiosadmin specified in it for "authorized_for" all of the items?:
Code: Select all
/usr/local/nagios/etc/cgi.cfg
Re: authorization Problem after update to 2.5
Hi,
strange .... I had to update a service config in ccm , and after applying this change the problem with authorization was gone
I don't know why, which would be interesting, but in case you have also no explanation you may close this.
Regards Andy
strange .... I had to update a service config in ccm , and after applying this change the problem with authorization was gone
I don't know why, which would be interesting, but in case you have also no explanation you may close this.
Regards Andy
Re: authorization Problem after update to 2.5
After the upgrade, did you fully log out and log back in to the XI interface? If not, this may explain your issues. Let us know if it recurs.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: authorization Problem after update to 2.5
Yes, I did logout, even rebooted the Server after i had seen the problem. But only after rewriting the config, the problem was solved.
Regards Andy
Regards Andy
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: authorization Problem after update to 2.5
Interesting, I can't really think of how this could effect a user's auth perms since they are in different databases. I suppose it could have had something to do with reconfigure access..