Richard, here is a copy of the pertinent section of my
Config.pm file. I have set up the LDAP auth params directly in that file
instead of through the GUI interface.
#Customer LDAP Auth Backend Settings
$Self->{'Customer::AuthModule'} =
'Kernel::System::CustomerAuth::LDAP';
$Self->{'Customer::AuthModule::LDAP::Host'} =
'10.222.129.234';
$Self->{'Customer::AuthModule::LDAP::BaseDN'} =
'dc=dbtamerica,dc=local';
$Self->{'Customer::AuthModule::LDAP::UID'} =
'sAMAccountName';
$Self->{'Customer::AuthModule::LDAP::SearchUserDN'} = 'cn=otrs
ldap,ou=users,ou=houston manufacturing pa,ou=dbt
america,dc=dbtamerica,dc=local';
$Self->{'Customer::AuthModule::LDAP::SearchUserPW'} =
'password';
#Customer User
#(customer user database backend and
settings)
$Self-> {CustomerUser} =
{
Name=>
'Database',
Module=>
'Kernel::System::CustomerUser::DB',
Params=> {Table => 'customer_user',
},
#customer uniq id
CustomerKey =>
'login',
CustomerID =>
'customer_id',
CustomerValid =>
'valid_id',
CustomerUserListFields => ['first_name',
'last_name', 'email'],
CustomerUserSearchFields =>
['login', 'last_name', 'customer_id'],
CustomerUserSearchPrefix => '',
CustomerUserSearchSuffix => '*',
CustomerUserSearchListLimit => 250,
CustomerUserPostMasterSearchFields => ['email'],
CustomerUserNameFields => ['salutation', 'first_name',
'last_name'],
Map =>
[
['UserSalutation', 'Salutation',
'salutation', 1, 0, 'var'],
['UserFirstname', 'Firstname', 'first_name', 1, 1,
'var'],
['UserLastname',
'Lastname', 'last_name', 1, 1,
'var'],
['UserLogin', 'Login',
'login', 1, 1, 'var'],
['UserPassword', 'Password', 'pw', 0, 1,
'var'],
['UserEmail', 'Email',
'email', 0, 1, 'var'],
['UserCustomerID', 'CustomerID', 'customer_id', 0, 1,
'var'],
['UserComment', 'Comment',
'comments', 1, 0, 'var'],
['ValidID', 'Valid', 'valid_id', 0, 1, 'int'],
],
};
#Customer User 1
#customer user ldap backend and
settings
$Self->{CustomerUser1} = {
Name => 'LDAP
Backend',
Module =>
'Kernel::System::CustomerUser::LDAP',
Params =>
{
Host
=>
'10.222.129.234',
BaseDN =>
'dc=dbtamerica,dc=local',
SSCOPE =>
'sub',
UserDN => 'cn=otrs ldap,ou=users,ou=houston manufacturing pa,ou=dbt
america,dc=dbtamerica,dc=local',
UserPw =>
'password',
AlwaysFilter =>
'',
SourceCharset =>
'utf-8',
DestCharset => 'iso-8859-1',
},
#customer uniq id
CustomerKey =>
'sAMAccountName',
CustomerID =>
'mail',
CustomerUserListFields => ['sAMAccountName',
'cn', 'mail'],
CustomerUserSearchFields =>
['sAMAccountName', 'cn', 'mail'],
CustomerUserSearchPrefix
=> '',
CustomerUserSearchSuffix =>
'*',
CustomerUserSearchListLimit =>
250,
CustomerUserPostMasterSearchFields =>
['mail'],
CustomerUserNameFields => ['givenname',
'sn'],
Map =>
[
['UserFirstname', 'Firstname',
'givenname', 1, 1, 'var'],
['UserLastname', 'Lastname', 'sn', 1, 1,
'var'],
['UserLogin', 'Login',
'sAMAccountName', 1, 1, 'var'],
['UserEmail', 'Email', 'mail', 1, 1,
'var'],
['UserCustomerID',
'CustomerID', 'mail', 0, 1,
'var'],
['UserPhone', 'Phone',
'telephonenumber', 1, 0, 'var'],
],
};
There was another follow-up email to this thread from
Tobias Lutticke, his suggestion may work as well and may be easier. I
have not tried his way, but will do so on my test system when I get a
chance. Hope this helps you.
-Tim
i have done the changes via the
sysconfig but now the changes are not in the comfig.pm
where can i find them?
the changes i made in the sysconfig are
Customer::AuthModule::LDAP::Host: = the FQDN of the ldap server
Customer::AuthModule::LDAP::BaseDN: = the base DN
Customer::AuthModule::LDAP::UID: =
uid
Customer::AuthModule::LDAP::UserAttr: = UID
Customer::AuthModule::LDAP::AlwaysFilter: = (objectClass=*)
Customer::AuthModule::LDAP::Params:
- async = 0
- port = 389
- timeout = 120
- version = 3
i hope this helps.
Regards
Richard Bosch
"Miller, Tim"
<Tim.Miller@dbtamerica.com> Sent by: otrs-bounces@otrs.org
08-01-2007 16:05
Please respond
to "User questions and discussions about OTRS.org"
<otrs@otrs.org> |
|
To
| "User questions and discussions
about OTRS.org" <otrs@otrs.org>
|
cc
|
|
Subject
| RE: [otrs] Panic no user
data |
|
Please post you Config.pm file so we can have a look. I
was having this same error trying to authenticate to a Windows AD via LDAP, and
got it working last week.
-Tim
From: otrs-bounces@otrs.org
[mailto:otrs-bounces@otrs.org] On Behalf Of
richard.bosch@bbraun.com
Sent: Monday, January 08, 2007 7:00
AM
To: otrs@otrs.org
Subject: [otrs] Panic no user
data
Hello,
i finaly got the LDAP authentication working with Lotus Notes but now
when i login to customer.pl i get the error Panic!
No UserData!!! and my
log says
CustomerUser: ****** authentification ok
(REMOTE_ADDR: *.*.*.*).
does anyone know how i can solve it?
Regards
Richard Bosch
********************************************************************************
The
information contained in this communication is confidential, may
be
attorney-client privileged, may constitute inside information, and is
intended
only for the use of the addressee. It is the property of the company
of the
sender of this e-mail. Unauthorized use, disclosure, or copying of
this
communication or any part thereof is strictly prohibited and may be
unlawful.
If you have received this communication in error, please notify us
immediately
by return e-mail and destroy this communication and all copies
thereof,
including all
attachments.
********************************************************************************
_______________________________________________
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 orr consulting for your
OTRS system?
=> http://www.otrs.com/
********************************************************************************
The information contained in this communication is confidential, may be
attorney-client privileged, may constitute inside information, and is intended
only for the use of the addressee. It is the property of the company of the
sender of this e-mail. Unauthorized use, disclosure, or copying of this
communication or any part thereof is strictly prohibited and may be unlawful.
If you have received this communication in error, please notify us immediately
by return e-mail and destroy this communication and all copies thereof,
including all attachments.
********************************************************************************