LDAP customer backend error when creating Tickets

Moderator: crythias

Locked
christianhutter
Znuny newbie
Posts: 4
Joined: 22 Mar 2011, 15:41
Znuny Version: 3.06

LDAP customer backend error when creating Tickets

Post by christianhutter »

I'm sorry if this has been handled before, I tried to find something here in the forums but failed to find a solution

I recently upgraded from otrs 2.3.x to 3.0.6. My customers are imported via LDAP from an Active Directory 2003/2008. All customers can log in normally and create tickets but if an agent tries to access the Tickets->New Ticket page on the agent interface he receives an error:

Code: Select all

Result of expression 'Core.Agent.CustomerSearch' [undefined] is not an object.

{anonymous}(TypeError: Result of expression 'Core.Agent.CustomerSearch' [undefined] is not an object.)
printStackTrace(#object)
{anonymous}(#function)
{anonymous}()
{anonymous}([object Event])
During the upgrade I did split the customer backend to connect to multiple sub containers of the AD as I was getting errors regarding the SiteLimit of the query. Might this be related? Its quite odd that the SiteLimit error still shows up as there are for sure less then then 1000 users in the sub container ( as far as i know AD will not deliver more then 1000 results without the client doing paging).

The customer backend part of my Config.pm looks as follows

Code: Select all

Self->{CustomerUser1} = {
    Name => 'LDAP Data Source',
    Module => 'Kernel::System::CustomerUser::LDAP',
    Params => {
        # ldap host
        Host => 'myldapserver.mydomain.com',
        # ldap base dn
        BaseDN => 'ou=container1,ou=Users,dc=mydomain,dc=com',
        # 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 => 'otrsuser@mydomain.com',
        UserPw => 'XXXXXX',
        # in case you want to add always one filter to each ldap query, use
        # this option. e. g. AlwaysFilter => '(mail=*)' or AlwaysFilter => '(objectclass=user)'
        AlwaysFilter => '(objectclass=user)',
      

        # if both your frontend and your LDAP are unicode, use this:
       SourceCharset => 'utf-8',
       DestCharset   => 'utf-8',

    },
    # customer unique id
    CustomerKey => 'sAMAccountName',
    # customer #
    CustomerID => 'sAMAccountName',
    CustomerUserListFields => ['cn', 'mail'],
    CustomerUserSearchFields => ['sAMAccountName', 'cn', 'mail'],
    CustomerUserSearchPrefix => '',
    CustomerUserSearchSuffix => '*',
    CustomerUserSearchListLimit => 999,
    CustomerUserPostMasterSearchFields => ['mail'],
    CustomerUserNameFields => ['givenname', 'sn'],
    # show not own tickets in customer panel, CompanyTickets
    CustomerUserExcludePrimaryCustomerID => 0,
    # add an ldap filter for valid users (expert setting)
#    CustomerUserValidFilter => '(!(description=locked))',
    # administrator can't change customer preferences
    AdminSetPreferences => 0,
#    # cache time to live in sec. - cache any database queries
#    CacheTTL => 0,
    Map => [
        # note: Login, Email and CustomerID are mandatory!
        # var, frontend, storage, shown (1=always,2=lite), required, storage-type, http-link, readonly
        [ 'UserTitle',      'Title',      'title',           1, 0, 'var', '', 0 ],
        [ 'UserFirstname',  'Firstname',  'givenname',       1, 1, 'var', '', 0 ],
        [ 'UserLastname',   'Lastname',   'sn',              1, 1, 'var', '', 0 ],
        [ 'UserLogin',      'Username',   'sAMAccountName',             1, 1, 'var', '', 0 ],
        [ 'UserEmail',      'Email',      'mail',            1, 1, 'var', '', 0 ],
        [ 'UserCustomerID', 'CustomerID', 'sAMAccountName',            0, 1, 'var', '', 0 ],
#        [ 'UserCustomerIDs', 'CustomerIDs', 'second_customer_ids', 1, 0, 'var', '', 0 ],
        [ 'UserPhone',      'Phone',      'telephonenumber', 1, 0, 'var', '', 0 ],
        [ 'UserAddress',    'Address',    'postaladdress',   1, 0, 'var', '', 0 ],
        [ 'UserComment',    'Comment',    'description',     1, 0, 'var', '', 0 ],
    ],
};

Any help would be very much appreciated, it happens quite often in our environment that agents will open tickets for a user...
christianhutter
Znuny newbie
Posts: 4
Joined: 22 Mar 2011, 15:41
Znuny Version: 3.06

Re: LDAP customer backend error when creating Tickets

Post by christianhutter »

If no one knows how to fix this, what about ideas how to further debug and analyze?
crythias
Moderator
Posts: 10170
Joined: 04 May 2010, 18:38
Znuny Version: 5.0.x
Location: SouthWest Florida, USA
Contact:

Re: LDAP customer backend error when creating Tickets

Post by crythias »

Is it possible you're using a 2.3 theme?
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
christianhutter
Znuny newbie
Posts: 4
Joined: 22 Mar 2011, 15:41
Znuny Version: 3.06

Re: LDAP customer backend error when creating Tickets

Post by christianhutter »

I followed the upgrade guideline - moving away the existing installation, unpacking the 3.0.6 tarball and running the upgrade scripts. So it should be impossible that I use an old theme?
christianhutter
Znuny newbie
Posts: 4
Joined: 22 Mar 2011, 15:41
Znuny Version: 3.06

Re: LDAP customer backend error when creating Tickets

Post by christianhutter »

I did end up doing a fresh installation with a clean database instead of upgrading. Now all is fine...
Locked