
On 08.02.2013 17:21, Steven Carr wrote:
On 8 February 2013 13:05, Israel Garcia
wrote: OK Steve, so I should edit /opt/otrs/Kernel/Config.pm, add my LDAP settings, restart OTRS and volia!? Also, I have seen in Admin/SysConfig/Frontend::Customer::Auth the same parameters I have added to /opt/otrs/Kernel/Config.pm, should I edit them using this web page or editing directly the /opt/otrs/Kernel/Config.pm file?
Don't quite know about the "voila", more like cross your fingers and hope it doesn't collapse in a heap.
One of my big issues with OTRS is the configuration is utter crap. Too
There are many places in OTRS which are crappy. E.g. different conflicting notification systems (see e.g. bug #8953), and, on-topic, customer groups. We have group attibute in LDAP for customers, and simple intuitive and SCALABLE solution would be just use that word of customer to regulate access. But "My Company tickets" in OTRS requires comma-delimited list of "user1,user2,...user100500" for EVERY user. Brain-damaged.
many places to configure things, everything should really be just configured through Sysconfig instead of having to mess about with text files (and perl based text files at that), and ideally stored in the database to make upgrades a lot easier than worrying about which config files you need and don't need.
I'm not sure the order in which the settings are applied but I would guess that anything you put in Kernel/Config.pm will override anything you configure in SysConfig (someone can correct me if I'm wrong).
Yes. Actually, Config.pm is applied TWO times: before SysConfig, and once again after.
So just make your changes in one place and one place only and they will be added to the overall config.
That's not always possible :)
--
Vadim Goncharov