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! 

_______________________________________________
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