-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
restricted users for event notification not working #391
Comments
Yup - correct. As of today, the event server does not filter events based on user permissions - it directly picks up alarms from shared memory for performance. The workaround, as you've discovered is to force specify the monitor list via zmNinja - this should be done by default, which I'll fix. |
hopefully fixed - please reopen if its not fixed in next release |
Thank you |
tried v1.2.30, the bug still exists |
Please do this:
Please post Debug logs of zmNinja and logs from zmeventserver |
actually never mind - I think I found the bug. |
Update to event server 0.92 required https://github.com/pliablepixels/zmeventserver/blob/master/zmeventnotification.pl |
@mafalb - did you try with the latest APK update ? You also need the updated event server (need to restart event server) |
closing - assuming resolved. Please re-open if it still is an issue |
Platform & OS Version
Windows 7
The version of the app you are reporting:
1.2.28
What is the nature of your issue
Bug
Details
I do have a zoneminder installation with 50+ cameras. zmtrigger.pl catches tcp notification from the cameras and begins to record. I also have a user who does have permissions to 3 cameras. When I start zmninja, zmeventnotification tells me in the log (I enhanced the logging slightly)
Events for every Camera is coming to zmninja (and thats a lot). I would have expected that only events for the 3 cameras are coming through.
If I go to Settings -> Save then the log messages changes
and after that only events from the specified cameras for that user are communicated to zmninja, it seems, which is the expected behaviour.
I think the initial authorisation goes wrong.
The text was updated successfully, but these errors were encountered: