Hi!
From reading the "Multiple Customer::AuthModule" thread
(http://lists.otrs.org/pipermail/otrs/2008-February/021994.html) I got
the impression that OTRS could use multiple auth modules for customers
in parallel.
However, the thread went on to simply being about LDAP authentication in
Active Directory :(
I happen to have a need for having multiple customer backends and auth
modules.
Reading some documents on the web gave lots of promises:
http://cunningcoder.org/node/9
http://doc.otrs.org/2.1/en/html/x1482.html#multible-customer-backends
However, it seems that currently OTRS _cannot_ work with two different
Customer authentication modules/sources, nor with two different Agent
authentication modules.
That's contrary to information from
Lars J�rgensen
(http://lists.otrs.org/pipermail/otrs/2008-February/021996.html) and
Michael Clay (http://cunningcoder.org/node/9).
Those postings are wrong, the configurations described there cannot
possibly work (well, unless I'm wrong, and I'd like to be wrong on this
one).
Here's why: when launching OTRS in debug mode 2 ("$Self->{Debug} = 2;"
in Config.pm), I can clearly see in the logs that OTRS doesn't even
attempt to read any "Customer::AuthModule1", "Customer::AuthModule2"
variables:
Debug: Config.pm ->Get('Customer::AuthModule') -->
Kernel::System::CustomerAuth::LDAP
There's no "Get('Customer::AuthModule1')" attempted anywhere.
So if you place something like this in Config.pm it won't matter to OTRS:
$Self->{'AuthModule1'} = 'Kernel::System::Auth::LDAP';
The only place where the number suffix variables are read by OTRS is for
CustomerUser configurations:
Debug: Config.pm ->Get('CustomerUser1') --> HASH(0x55555a12a620)
Debug: Config.pm ->Get('CustomerUser2') --> HASH(0x55555a12b910)
However, those don't influence Customer Auth - they only influence
storage of tickets if I understand that correctly.
So if you want to handle multiple customer authentication modules, I've
found out the only way is to write a non-standard Customer Auth module,
like Ralf Becker did in 2006:
http://lists.otrs.org/pipermail/otrs/2006-June/011413.html
Better yet, of course, is to use Ralf's module, which luckily is still
available under the old address
(http://www.fh-trier.de/~beckerr/OTRS-CustomerAuth/Multiple.pm). I've
tested this module on OTRS 2.1 and it still works!
A final question: maybe I'm wrong and it actually is possible to use
multiple Customer::Auth modules in latest versions of OTRS? If yes, then
how? Lars J�rgensen's and Michael Clay's setup definitely don't work for
me (using OTRS 2.1).
--
Best Regards,
Aleksander Adamowski
GG#: 274614
ICQ UIN: 19780575
http://olo.org.pl
--
Aleksander Adamowski
Administrator systemów korporacyjnych; Instruktor
Altkom Akademia S.A. http://www.altkom.pl
Warszawa, ul. Chłodna 51
tel. brak
kom. +48 601-318-080
Sąd Rejonowy dla m.st. Warszawy w Warszawie, XII Wydział Gospodarczy Krajowego
Rejestru Sądowego,
KRS: 0000120139, NIP 118-00-08-391, Kapitał zakładowy: 1000 000 PLN. Adres
rejestrowy Firmy - ul. Stawki 2, 00-193 Warszawa.
Niniejsza wiadomość zawiera informacje zastrzeżone i stanowiące tajemnicę
przedsiębiorstwa firmy Altkom Akademia S.A.
Ujawnianie tych informacji osobom trzecim lub nieuprawnione wykorzystanie ich
do własnych celów jest zabronione.
Jeżeli otrzymaliście Państwo niniejszą wiadomość omyłkowo, prosimy o
niezwłoczne skontaktowanie się z nadawcą oraz usunięcie wszelkich kopii
niniejszej wiadomości.
This message contains proprietary information and trade secrets of Altkom
Akademia S.A. company.
Unauthorized use or disclosure of this information to any third party is
prohibited.
If you received this message by mistake, please contact the sender immediately and delete all copies of this message.
_______________________________________________
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
Support or consulting for your OTRS system?
=> http://www.otrs.com/
