You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
Assignee: (none)
Status: Rejected (closed on 2013-03-11 12:37:19 +00:00)
Target Version: (none)
Last Update: 2013-03-11 12:37:19 +00:00 (in Redmine)
Currently the PNP Integration in Icinga does not have any security checking. If you know the URL to any PNP Chart, you can easily view other charts, even if you do not have access to them. It would be great if PNP does not deliver the HTML code of PNP directly, instead we could create a Icinga PHP file that checks user restrictions first, and then query PNP for the data and deliver that data to the user. PNP itself can than be restricted with an htaccess setting to not deliver content directly. but only via Icinga's script.
The text was updated successfully, but these errors were encountered:
This issue has been migrated from Redmine: https://dev.icinga.com/issues/1279
Created by jhein on 2011-03-08 10:56:47 +00:00
Assignee: (none)
Status: Rejected (closed on 2013-03-11 12:37:19 +00:00)
Target Version: (none)
Last Update: 2013-03-11 12:37:19 +00:00 (in Redmine)
Currently the PNP Integration in Icinga does not have any security checking. If you know the URL to any PNP Chart, you can easily view other charts, even if you do not have access to them. It would be great if PNP does not deliver the HTML code of PNP directly, instead we could create a Icinga PHP file that checks user restrictions first, and then query PNP for the data and deliver that data to the user. PNP itself can than be restricted with an htaccess setting to not deliver content directly. but only via Icinga's script.
The text was updated successfully, but these errors were encountered: