On 24 Jun 2009, at 16:03, Craig Pendleton wrote:
Thanks for the reply and the FAQ, Ton. I’m pretty certain that no
change was made manually to cause this – I am the primary user of
opsview and didn’t make any changes following the upgrade.
I followed the directions in the FAQ entry, and ADMINACCESS is
already defined for our admin contacts. Each admin contact looks
like the following:
+-----------------------+--------+----------+----------------+
| contact_name | roleid | accessid | name |
+-----------------------+--------+----------+----------------+
| admin | 10 | 1 | VIEWALL |
| admin | 10 | 3 | ACTIONALL |
| admin | 10 | 6 | NOTIFYSOME |
| admin | 10 | 7 | CONFIGUREHOSTS |
| admin | 10 | 8 | RELOADACCESS |
| admin | 10 | 9 | ADMINACCESS |
I tried again with the “admin” contact as well as my own contact
(which previously had admin rights) and still no luck. I get
“Access Denied” for anything under /admin.
Anything else I should be looking at? I am proxying with Apache,
if that makes any difference.
Are you proxying under a different path?
Did this work after the upgrade?
The definitions for what is allowed under particular paths are in /usr/
local/opsview-web/lib/Opsview/Web.pm, but I can't see how that would
have been changed.
Ton
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/listinfo/opsview-users
