Agent LDAP Sync doesn't appear to work at all in OTRS 2.4! This worked great in 2.3, but appears completely broken in 2.4, even when following the *exact* sample config shown in the admin book, or using a known-good configuration that worked in 2.3. After upgrading to 2.4, new users are not able to log. They get the error: Panic, user authenticated but no user data can be found in OTRS DB!! Perhaps the user is invalid. I've seen others post on the list with similar errors, and none of those problems were resolved to my knowledge. Users: Do NOT upgrade to OTRS 2.4 if you use LDAP sync for agents, because it will not work no one will help you! OTRS STAFF -- IF THIS IS BROKEN PLEASE LET US KNOW!! Or give us some info to help troubleshoot or debug the problem. Does anyone know if the old LDAP module from 2.3 can be used with 2.4? Thanks, Josh Higgins
It looks like your details from the ldap tree are not being copied to
your OTRS DB.
Here's my config for LDAP on 2.4 which successfully authenticates
users from Active Directory to OTRS
# LDAP Authentication Options
$Self->{'AuthModule'} = 'Kernel::System::Auth::LDAP';
$Self->{'AuthModule::LDAP::Host'} = 'host.example.com';
$Self->{'AuthModule::LDAP::BaseDN'} = 'dc=example, dc=com';
$Self->{'AuthModule::LDAP::UID'} = 'sAMAccountName';
$Self->{'AuthModule::LDAP::UserAttr'} = 'DN';
# This is the user that is used to run LDAP queries as.
$Self->{'AuthModule::LDAP::SearchUserDN'} = 'CN=OTRS
Administrator,CN=Users,DC=example,DC=com';
$Self->{'AuthModule::LDAP::SearchUserPw'} = 'PassW0rd';
# LDAP Auth DB sync options. This copys the data from LDAP to the OTRS DB
$Self->{'AuthSyncModule'} = 'Kernel::System::Auth::Sync::LDAP';
$Self->{'AuthSyncModule::LDAP::Host'} = 'ldap://host.example.com/';
$Self->{'AuthSyncModule::LDAP::BaseDN'} = 'dc=example, dc=com';
$Self->{'AuthSyncModule::LDAP::UID'} = 'sAMAccountName';
$Self->{'AuthSyncModule::LDAP::SearchUserDN'} = 'CN=OTRS
Administrator,CN=Users,DC=example,DC=com';
$Self->{'AuthSyncModule::LDAP::SearchUserPw'} = 'PassW0rd';
$Self->{'AuthSyncModule::LDAP::UserSyncMap'} = {
# DB -> LDAP
UserFirstname => 'givenName',
UserLastname => 'sn',
UserEmail => 'mail',
};
Try that on your system and see if it works for you.
Rory
--
Support my 365 Challenge in aid of the Irish Cancer Society
www.365challenge.ie
2009/10/28 Josh Higgins
Agent LDAP Sync doesn't appear to work at all in OTRS 2.4! This worked great in 2.3, but appears completely broken in 2.4, even when following the *exact* sample config shown in the admin book, or using a known-good configuration that worked in 2.3.
After upgrading to 2.4, new users are not able to log. They get the error: Panic, user authenticated but no user data can be found in OTRS DB!! Perhaps the user is invalid.
I've seen others post on the list with similar errors, and none of those problems were resolved to my knowledge.
Users: Do NOT upgrade to OTRS 2.4 if you use LDAP sync for agents, because it will not work no one will help you!
OTRS STAFF -- IF THIS IS BROKEN PLEASE LET US KNOW!! Or give us some info to help troubleshoot or debug the problem.
Does anyone know if the old LDAP module from 2.3 can be used with 2.4?
Thanks, Josh Higgins --------------------------------------------------------------------- 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
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/
Hi Josh, I am sorry to hear you are having issues. But, please rest assured that all is well. Look at the difference between the 2.3 and the 2.4 http://source.otrs.org/viewvc.cgi/otrs/Kernel/Config/Defaults.pm?r1=1.323&r2... You will see that the configuration has changed ever so slightly (Line391-Line411) This will be causing your problem. Hope you get it up and running now. On Oct 28, 2009, at 5:03 PM, Josh Higgins wrote:
Agent LDAP Sync doesn't appear to work at all in OTRS 2.4! This worked great in 2.3, but appears completely broken in 2.4, even when following the *exact* sample config shown in the admin book, or using a known- good configuration that worked in 2.3.
After upgrading to 2.4, new users are not able to log. They get the error: Panic, user authenticated but no user data can be found in OTRS DB!! Perhaps the user is invalid.
I've seen others post on the list with similar errors, and none of those problems were resolved to my knowledge.
Users: Do NOT upgrade to OTRS 2.4 if you use LDAP sync for agents, because it will not work no one will help you!
OTRS STAFF -- IF THIS IS BROKEN PLEASE LET US KNOW!! Or give us some info to help troubleshoot or debug the problem.
Does anyone know if the old LDAP module from 2.3 can be used with 2.4?
-- Shawn Beasley shawn@otrs.org Computers make work that one would not have without them go faster!
participants (3)
-
Josh Higgins -
Rory -
Shawn Beasley