On 26.01.2010, at 10:43, Михаил Лукин wrote:
A number of basic ACLs is what we need most of the time. As I understand, simple ACL is just Perl dictionary of dictionaries (they are called "dictionaries" in Python, in Perl it is maybe Hash or smth like this, I don't remember).
For example, I need to limit choices of SLAs and Priorities by customer department or title (customer data is in LDAP), and it's gonna be a lot of similar and very simple ACLs.
On another hand, I would be completely satisfied if I could place those ACLs somewhere out of Config.pm (f.e. CustomConfig01.pm for ACLs, CustomConfig02.pm for backends and so on).
On Tue, Jan 26, 2010 at 12:26 PM, Shawn Beasley
<shawn.beasley@otrs.com> wrote:
Hi Mihail,
On Jan 26, 2010, at 10:17 , Михаил Лукин wrote:
> There is a nice example of editing ACL via Sysconfig (Ticket -> Core::TicketACL)
> Is there an OTRS package or something else to allow Add/Edit new ACLs via web interface (Sysconfig)?
Unfortunately, not currently. It should be easy to implement a static number of basic configurable ACLs. Due to the complexity, it makes it harder to implement this in its full power.
I am sure there will be a Sysconfig Group which does allow ACL configuration, it should be very easy.
However, currently you can remove the ACLs from Config.pm, actually as everything else, by saving a new file (e.g. ACL.pm) in $OTRS_HOME/Kernel/Config/Files/
Just make sure the syntax is ok. Im my cases i just copy the ZZZAuto.pm basic structure and put in the ACLs that I want to be active.
My current ACL.pm file is attached and is working but not tested in production environments yet.