Dear List, I've just entered all the customerdata from our groupware database into the LDAP directory. The entries went into the LDAP as UTF8 converted strings. Now the CustomerUser function works for searching etc., BUT all german Umlaute are not displayed correctly by OTRS. All other applications that can read this LDAP directory display the data in the correct way, so I think it must be an OTRS bug. Any comments? Thanks, Matthias
Hi Matthias, On Fri, Aug 27, 2004 at 12:57:33PM +0200, Matthias Eichler wrote:
I've just entered all the customerdata from our groupware database into the LDAP directory. The entries went into the LDAP as UTF8 converted strings.
Now the CustomerUser function works for searching etc., BUT all german Umlaute are not displayed correctly by OTRS. All other applications that can read this LDAP directory display the data in the correct way, so I think it must be an OTRS bug.
Any comments?
It depends on the application charset. OTRS also can work/display LDAP UTF8 converted strings correctly. Solutions: a) Let OTRS work in UTF-8 charset (then you also need a utf-8 able database, e. g. MySQL 4.1 or higher) b) Convert UTF-8 to e. g. iso-8859-1 which config settings in CustomerUser config object: [...] $Self->{CustomerUser} = { Name => 'LDAP Backend', [...] Params => { # ldap host Host => 'ldap.example.com', # ldap base dn BaseDN => 'ou=seas,o=csuh', # search scope (one|sub) # if your frontend is e. g. iso-8859-1 and the charset of your # ldap server is utf-8, use this options (if not, ignore it) SourceCharset => 'utf-8', DestCharset => 'iso-8859-1', }, [...] [...] Anyway, if you need business support to get fast and phone help, contact ((otrs.de)).
Matthias
Martin Edenhofer -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!
Hi Martin, Am Dienstag, den 31.08.2004, 06:44 +0200 schrieb Martin Edenhofer:
a) Let OTRS work in UTF-8 charset (then you also need a utf-8 able database, e. g. MySQL 4.1 or higher) b) Convert UTF-8 to e. g. iso-8859-1 which config settings in CustomerUser config object:
Hm...is some special version needed for this translation feature? We've 1.2.2 an I get: Premature end of script headers: /var/otrs/bin/cgi-bin/index.pl Undefined subroutine &Kernel::Config::Defaults::DestCharset called at /var/otrs/bin/cgi-bin/../../Kernel/Config/Defaults.pm line 1453.
Anyway, if you need business support to get fast and phone help, contact ((otrs.de)).
Sure, if there are really tough things to do we will call, but in my eyes this is just a configuration or documentation problem ;-) Thanks, Matthias Eichler
Hi Matthias, On Tue, Aug 31, 2004 at 09:57:28AM +0200, Matthias Eichler wrote:
a) Let OTRS work in UTF-8 charset (then you also need a utf-8 able database, e. g. MySQL 4.1 or higher) b) Convert UTF-8 to e. g. iso-8859-1 which config settings in CustomerUser config object:
Hm...is some special version needed for this translation feature? We've 1.2.2 an I get: Premature end of script headers: /var/otrs/bin/cgi-bin/index.pl Undefined subroutine &Kernel::Config::Defaults::DestCharset called at /var/otrs/bin/cgi-bin/../../Kernel/Config/Defaults.pm line 1453.
It looks like an perl syntax error in Kernel/Config/Defaults.pm. Anyway, if you use OTRS 1.2.2, follow the following: o Update Kernel/System/CustomerUser/LDAP.pm to 1.16 o Don't change Kernel/Config/Defaults.pm because it's updated with every new OTRS version. Learn more about the config file mechanism: http://doc.otrs.org/1.2/en/html/configfile.html o Add your new CustomerUser config option to Kernel/Config.pm like this one and change your options: [Kernel/Config.pm] $Self->{CustomerUser} = { Name => 'LDAP Backend', Module => 'Kernel::System::CustomerUser::LDAP', Params => { # ldap host Host => 'example.ldap.com', # ldap base dn BaseDN => 'ou=seas,o=csuh', # search scope (one|sub) SSCOPE => 'sub', # The following is valid but would only be necessary if the # anonymous user does NOT have permission to read from the LDAP tree UserDN => '', UserPw => '', # if your frontend is e. g. iso-8859-1 and the charset of your # ldap server is utf-8, use this options (if not, ignore it) SourceCharset => 'utf-8', DestCharset => 'iso-8859-1', }, # customer uniq id CustomerKey => 'uid', # customer # CustomerID => 'mail', CustomerUserListFields => ['cn', 'mail'], CustomerUserSearchFields => ['uid', 'cn', 'mail'], CustomerUserPostMasterSearchFields => ['mail'], CustomerUserNameFields => ['givenname', 'sn'], Map => [ # note: Login, Email and CustomerID needed! # var, frontend, storage, shown, required, storage-type [ 'UserSalutation', 'Title', 'title', 1, 0, 'var' ], [ 'UserFirstname', 'Firstname', 'givenname', 1, 1, 'var' ], [ 'UserLastname', 'Lastname', 'sn', 1, 1, 'var' ], [ 'UserLogin', 'Login', 'uid', 1, 1, 'var' ], [ 'UserEmail', 'Email', 'mail', 1, 1, 'var' ], [ 'UserCustomerID', 'CustomerID', 'mail', 0, 1, 'var' ], [ 'UserPhone', 'Phone', 'telephonenumber', 1, 0, 'var' ], [ 'UserAddress', 'Address', 'postaladdress', 1, 0, 'var' ], [ 'UserComment', 'Comment', 'description', 1, 0, 'var' ], ], }; Then it should work.
Matthias Eichler
Martin Edenhofer -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!
Hi,
Anyway, if you use OTRS 1.2.2, follow the following: o Update Kernel/System/CustomerUser/LDAP.pm to 1.16
Ok, here is my problem number on: in your package otrs-1.2.4-01 the version of LDAP.pm is 1.15 In your packages otrs-1.3.x the version of LDAP.pm is 1.21 Is the exact version important or is it >=1.16? I am asking this becaus of the sencond problem, more to read downwards...
o Don't change Kernel/Config/Defaults.pm because it's updated with every new OTRS version. Learn more about the config file mechanism: http://doc.otrs.org/1.2/en/html/configfile.html
That's clear.
o Add your new CustomerUser config option to Kernel/Config.pm like this one and change your options: [...] Then it should work.
Unfortunately it doenst...I can see the LDAP entries, but the UTF-8 parts are not good. For example Jürgen is printed in the dropdown of OTRS as "JÃŒrgen". Here is my Config.pm part: ---cut--- # ---------------------------------------------------- # # CustomerUser configuration # # ---------------------------------------------------- # # This is an example configuration for an LDAP auth. backend. # (take care that Net::LDAP is installed!) $Self->{'Customer::AuthModule'} = 'Kernel::System::CustomerAuth::LDAP'; $Self->{'Customer::AuthModule::LDAP::Host'} = 'ldap.kernzeit.loc'; $Self->{'Customer::AuthModule::LDAP::BaseDN'} = 'dc=kernzeit,dc=com'; $Self->{'Customer::AuthModule::LDAP::UID'} = 'uid'; $Self->{'Customer::AuthModule::LDAP::GroupDN'} = 'cn=customer,ou=groups,ou=nss,dc=kernzeit,dc=com'; $Self->{'Customer::AuthModule::LDAP::AccessAttr'} = 'memberUid'; $Self->{'Customer::AuthModule::LDAP::UserAttr'} = 'UID'; $Self->{'Customer::AuthModule::LDAP::SearchUserDN'} = 'dc=kernzeit,dc=com'; $Self->{'Customer::AuthModule::LDAP::SearchUserPw'} = 'ourpassword'; # CustomerUser # (customer user ldap backend and settings) $Self->{CustomerUser} = { Name => 'LDAP Backend', Module => 'Kernel::System::CustomerUser::LDAP', Params => { Host => 'ldap.kernzeit.loc', BaseDN => 'ou=ogo,dc=kernzeit,dc=com', SSCOPE => 'sub', UserDN => 'dc=kernzeit,dc=com', UserPw => 'ourpassword', SourceCharset => 'utf-8', DestCharset => 'iso-8859-1', }, CustomerKey => 'uid', CustomerID => 'o', CustomerUserListFields => ['cn', 'o', 'mail'], CustomerUserSearchFields => ['uid', 'sn', 'givenName', 'cn', 'mail', 'o'], CustomerUserPostMasterSearchFields => ['mail'], CustomerUserNameFields => ['givenname', 'sn'], Map => [ [ 'UserSalutation', 'Title', 'title', 1, 0, 'var' ], [ 'UserFirstname', 'Firstname', 'givenName', 1, 1, 'var' ], [ 'UserLastname', 'Lastname', 'sn', 1, 1, 'var' ], [ 'UserLogin', 'Login', 'uid', 1, 1, 'var' ], [ 'UserEmail', 'Email', 'mail', 1, 1, 'var' ], [ 'UserCustomerID', 'CustomerID', 'o', 0, 1, 'var' ], [ 'UserPhone', 'Phone', 'telephoneNumber', 1, 0, 'var' ], [ 'UserAddress', 'Address', 'postalAddress', 1, 0, 'var' ], [ 'UserComment', 'Comment', 'description', 1, 0, 'var' ], ], }; ---cut--- Is it a bug or am I too dumb? Thanks, Matthias Eichler
participants (2)
-
Martin Edenhofer -
Matthias Eichler