Page 1 of 1
Prevent that user can delete filter purgewhenfull
Posted: Tue Sep 18, 2012 4:31 pm
by biologisch
Hi there!
Is it possible to prevent that user can delete the "purgewhenfull" Filter. Or is it possible to block the filter button for all users?
Thx,
biologisch
Re: Prevent that user can delete filter purgewhenfull
Posted: Tue Sep 18, 2012 7:44 pm
by jonathancnewcomb
You should be able to give them the permission "None" to System and that should prevent users from removing filters
Re: Prevent that user can delete filter purgewhenfull
Posted: Tue Sep 18, 2012 7:51 pm
by biologisch
Hi!
Thanks for your quick response but thats not the right way. The user can delete it without "system" permissions.
Greets,
biologisch
Re: Prevent that user can delete filter purgewhenfull
Posted: Tue Sep 18, 2012 7:56 pm
by jonathancnewcomb
Ok, then maybe I was mistaken, I have created read-only users on my system that can view events and execute filters and the like, but can not delete, archive or remove or create filters. I have the following permissions set on these users and they do not have the "Save" or "Delete" buttons on the filters menu:
Enabled: yes
Stream: View
Events: View
Control: None
Monitors: View
System: None
Bandwidth: High (local users)
They have the filter button (no way to remove it) but they can not delete or modify the filters
Re: Prevent that user can delete filter purgewhenfull
Posted: Wed Sep 19, 2012 6:14 am
by biologisch
I get it!
Search in .../skins/classic/views/console.php
<?= makePopupButton( '?view=filter&filter[terms][0][attr]=DateTime&filter[terms][0][op]=%3c&filter[terms][0][val]=now', 'zmFilter', 'filter', $SLANG['Fil
ters'], canView( 'Events' ) ) ?>
replace with
<?= makePopupButton( '?view=filter&filter[terms][0][attr]=DateTime&filter[terms][0][op]=%3c&filter[terms][0][val]=now', 'zmFilter', 'filter', $SLANG['Fil
ters'], canView( 'System' ) ) ?>
Re: Prevent that user can delete filter purgewhenfull
Posted: Wed Sep 19, 2012 6:22 pm
by jonathancnewcomb
hmm looks like you just changed it from a "Event" group to a "System" group for that button. Pretty good thinking (probably where it should have been to begin with)