Hi Bruno,
On Tue, Jan 31, 2012 at 10:42, Bruno Cardon bruno.car...@ugent.be wrote:
Is it possible to give the rpc user read-only access so he cannot, for
example, add a ticket to the otrs-system ?
The RPC user is not a 'real' OTRS user; via the RPC interface you
actually expose a part of the API and you'd expose FULL access. By
specifying the UserID when you create a ticket you for instance can
set any user as the ticket creator.
With upcoming OTRS 3.1 (betas already available) we'll also have a new
SOAP interface, complete with WSDLs, where you can authenticate with
agent or customer permissions, and then only can see tickets for this
agent and/or customer; this might be of interest to you.
Also, the current iPhone handle exposes ticket functionality via JSON.
The iPhone handle also requires agent permissions and would enforce
the normal OTRS permission structure.
Kindest regards,
Michiel Beijen
Senior Consultant
OTRS BV
Schipholweg 103
2316 XC Leiden
The Netherlands
T: +31 71 8200 255
F: +31 71 8200 254
I: http://www.otrs.com
Making OTRS even better! Exclusive Feature Add-Ons improve usability
of OTRS and extend its functionality: http://j.mp/ndQvZj
-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
