Thanks Matthias for your answer!
Our aim was to keep it as simple as it could, so I'll probably stay with
default behavior then.
Regards,
Samuel
On 08/18/2015 05:45 PM, Matthias Jentsch wrote:
Hi Samuel,
what you can do is create a role that imposes a very strict filter on
all users and groups and just make sure that any new user is a member of
it. As described in the chapter about stacking different filters (
https://github.com/Icinga/icingaweb2/blob/master/doc/security.md#stacking-filters
), additional filters can be used to give the permissions back to
certain users or user groups.
So basically what you want is possible, but requires a little bit of
configuration effort.
Best regards,
Matthias
Am 18.08.2015 um 15:12 schrieb Bancal Samuel:
As seen in
https://github.com/Icinga/icingaweb2/blob/master/doc/security.md#objects
,
"By default a user can see everything, but it is possible to
explicitly restrict what each user can see using restrictions."
Would it be possible to force opposite behavior?
By default a user can't see anything, but it is possible to show him
the servers he is responsible for?
Thanks,
Samuel
--
Matthias Jentsch
Application Developer
NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
Tel: +49 911 92885-0 | Fax: +49 911 92885-77
GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
http://www.netways.de | [email protected]
** OSBConf 2015 - September - osbconf.org **
** OSMC 2015 - November - netways.de/osmc **
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
--
Samuel Bancal
ENAC-IT
EPFL
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
