Hi all!

Boring subject, but I'm in despair.
After several days epic battle with LDAP's, docs, lists (all messages here), configs and so on I'm totally stuck with this.


Short pre-history:
- LDAP server is M$ Actite Directory, Windows 2000 server;
- Linux distribution, RedHat 8.0 (all paches applied);
- OTRS v1.2.2 (last one)
- Apache Web server 2.0.40
- local DB authentication with no problems;

Configuration part from Config.pm:
$Self->{'Customer::AuthModule'} = 'Kernel::System::CustomerAuth::LDAP'; # pretty trivial, local DB config is commented
$Self->{'AuthModule::LDAP::Host'} = 'heb-hdo-dc-03.hebros.bg';
# my W2K server, DC and LDAP server)
$Self->{'AuthModule::LDAP::BaseDN'} = 'dc=hebros,dc=bg';
# My baseDN, why there is different sintaxis? What is correct one "dc" or "ou"/"o"?
$Self->{'AuthModule::LDAP::UID'} = 'uid';
# I'm not sure is this correct, but left untouched


Error: When I've restart Apache and go to Customer-User URL (customer.pl script): this error apear:

*******
Server error!
The server encountered an internal error and was unable to complete your request.
Error message:
Need Customer::AuthModule::LDAPHost in Kernel/Config.pm at /opt/otrs/Kernel/cpan-lib/CGI/Carp.pm line 301, <DATA> line 225.
If you think this is a server error, please contact the webmaster
Error 500
********


Ones again: when local authentication occure, everithing is OK.

Any ideas? Any help will be very appreciated! This is my first attemp to link OTRS with LDAP server and I'm afraid, that this is only a begining.

--
Best regards,
Vladimir Gerdjikov

Communication and NOS Manager, HebrosBank Head Office, +359 32/903435,
+359 888 578 458
KeyID:BC821E9B from http://wwwkeys.uk.pgp.net
Fingerprint: 503C 54EE C1B0 B446 DD84  5A3A 4E05 4D62 BC82 1E9B

_______________________________________________
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 oder Consulting f�r Ihr OTRS System?
=> http://www.otrs.de/

Reply via email to