[icinga-devel] CGI AUTH and restrict a user to read only ( patch )

Serge Noiraud Serge.Noiraud at bull.net
Wed Feb 1 14:35:27 CET 2012


Le 01/02/2012 14:10, Ricardo a écrit :
> Hi,
>
> Then we should add a check at beginning of cmd.cgi.
>
> Thought this is already the case but maybe not.
There is nothing to do. I'm sorry for the noise.
I didn't know the directive I added already exists. So it works like a 
charm.

>
> Ricardo
>
> Am 01.02.2012 um 13:34 schrieb Serge Noiraud <Serge.Noiraud at bull.net 
> <mailto:Serge.Noiraud at bull.net>>:
>
>> Le 01/02/2012 12:48, Matthew Brooks a écrit :
>>> On Wed, Feb 1, 2012 at 02:27, Serge Noiraud <Serge.Noiraud at bull.net 
>>> <mailto:Serge.Noiraud at bull.net>> wrote:
>>>
>>>     Hi,
>>>
>>>     This the first time I send a request to this list.
>>>
>>>     My problem description :
>>>     I have some users associated by their contact to some hosts.
>>>     They can see all services and all hosts associated with their
>>>     user account.
>>>     Ok, it works very well.
>>>     BUT, they can send commands for those hosts and services.
>>>     I want them to be read only.
>>>
>>>     I couln't find a solution for this.
>>>
>>>
>>>
>>> For the contact configuration for those contacts add:
>>>
>>> can_submit_commands             0
>>>
>>> For more information see 
>>> http://docs.icinga.org/latest/en/objectdefinitions.html#objectdefinitions-contact
>> I knew that, but I didn't want the users see all possibles commands.
>> With this setting, you select a command, then you click on submit, 
>> then you click on commit.
>> You know only at this moment you don't have access to this. It's too 
>> late !

Serge
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.icinga.org/pipermail/icinga-devel/attachments/20120201/67585b5f/attachment.html>


More information about the icinga-devel mailing list