Thomas,

I did this already to clean up the view when looking through the customer Management 
screen.  As for the showing all the groups I think you would have to do a for 
statement for each memberof line in the ldap directory for that particular user and 
then add the results of those searches to an array and then display the array.

The only problem is that I'm not much for perl programming.  I will try and teach 
myself but should anyone be able to perform this faster please let me know.

Later....

Neil

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Nilsen
Sent: Friday, November 21, 2003 6:43 AM
To: User questions and discussions about OTRS.
Subject: RE: [otrs] Adding LDAP Customer Info


Neil,

Look at http://www.mail-archive.com/[EMAIL PROTECTED]/msg02199.html for info on how I 
got rid of some of the extra AD info (this will also remove groups!). However, I'm not 
sure how you would solve your issue to show all the groups the users is a member of..

Thomas

>-----Original Message-----
>From: Neil Lehouillier [mailto:[EMAIL PROTECTED]
>Sent: Thursday, November 20, 2003 5:20 PM
>To: User questions and discussions about OTRS.
>Subject: RE: [otrs] Adding LDAP Customer Info
>
>
>Thomas,
>
>thanks a lot.  Everything seems to be working perfectly with
>the integration into Active Directory.  Just a couple of 
>questions.....:
>
>1.  With email-address or text that is too large to fit on the
>Phone View Customer Info side of the screen... is there anyway 
>to get this information to wrap or to setup a web fix so that 
>when you hold the mouse over the information it brings up a 
>little box with the full information(last one difficult I'm 
>pretty sure)?
>
>2.  In the Phone view customer info side of the screen I set
>up a Groups field that shows the users group membership.  But 
>it only shows the first one.  Is there anyway to get it to 
>show all the groups and to filter out the extraneous 
>information 
>(ie....CN=Accounting,OU=Distribution,OU=Groups,DC=domain,DC=loc
>al..... All I want to see is the CN=Accounting).
>
>Here is an example of the membership information on one user:
>memberOf: CN=Audit,OU=Secret,OU=Groups,DC=domain,DC=local
>memberOf: CN=Snr Accountants,OU=Secret,OU=Groups,DC=domain,DC=local
>memberOf: CN=Accounting,OU=Distribution,OU=Groups,DC=domain,DC=local
>memberOf: CN=All Staff,OU=Distribution,OU=Groups,DC=domain,DC=local
>memberOf: CN=Hornet,OU=Secret,OU=Groups,DC=domain,DC=local
>memberOf: CN=Accounting,OU=Secret,OU=Groups,DC=domain,DC=local
>memberOf: CN=Users,CN=Builtin,DC=domain,DC=local
>
>Later....
>
>Thanks...
>
>Neil
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
>Behalf Of Thomas Nilsen
>Sent: Thursday, November 20, 2003 8:36 AM
>To: User questions and discussions about OTRS.
>Subject: RE: [otrs] Adding LDAP Customer Info
>
>
>Try changing CustomerKey to sAMAccountName. AD doesn't use uid
>for the useraccounts.
>
>Thomas
>
>>-----Original Message-----
>>From: Neil Lehouillier [mailto:[EMAIL PROTECTED]
>>Sent: Thursday, November 20, 2003 4:27 PM
>>To: User questions and discussions about OTRS.
>>Subject: RE: [otrs] Adding LDAP Customer Info
>>
>>
>>I tried what you said and entered the following into my
>Config.pm file:
>>
>>        # customer uniq id
>>        CustomerKey => 'uid',
>>        # customer #
>>        CustomerID => 'mail',
>>        CustomerUserListFields => ['sAMAccountName', 'cn', 'mail'],
>>        CustomerUserSearchFields => ['sAMAccountName', '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', 'ldap_attr_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',
>>'ldap_attr_telephoneNumber', 1, 0, 'var' ],
>>            [ 'UserAddress', 'Address', 'postaladdress', 1, 
>0, 'var' ],
>>            [ 'UserComment', 'Comment', 'description', 1, 0, 'var' ],
>>        ],
>>    };
>>
>>When I perform the search I don't see anything more on the screen.
>>
>>In the System Log of OTRS it shows this:
>>Thu Nov 20 08:19:23 2003 error OTRS-CGI-10 Need User or CustomerID!
>>
>>Shouldn't it be able to grab the customer id from the CustomerID => 
>>'mail' field?
>>
>>Later....
>>
>>
>>Thanks for the help.....
>>
>>Neil
>>
>>
>>
>>
>>-----Original Message-----
>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf 
>>Of Martin Edenhofer
>>Sent: Wednesday, November 19, 2003 3:42 PM
>>To: User questions and discussions about OTRS.
>>Subject: Re: [otrs] Adding LDAP Customer Info
>>
>>
>>Hi Neil,
>>
>>On Wed, Nov 19, 2003 at 09:39:17AM -0700, Neil Lehouillier wrote:
>>> thanks for responding so quickly.  This config allows me to
>>search by
>>> user id which is something I was looking for but it still doesn't 
>>> answer my first two questions.  What I want is to include more 
>>> information for teh tech guys in the ticket view.  When I click on 
>>> phone view and then enter a user name I want otrs to display
>>the user
>>> information such as Full Name, Phone #, Email Address, and Office 
>>> number(all of which is entered in Active Directory) on
>>either the side
>>> of the screen where it says Customer Info or within the first couple 
>>> of lines of the text of the ticket.  Is this possible?
>>
>>Yes, you can do this. Add more to the Map of the CustomerUser config
>>option:
>>
>>   $Self->{CustomerUser} = {
>>   [...]
>>      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' ],
>>           [ 'UserHost', 'Host', 'ldap_attr_host', 1, 0, 'var' ],
>>           [ 'UserIP', 'Host IP', 'ldap_attr_host_ip', 1, 0, 'var' ],
>>           [ 'UserXxxx', 'Xxxx', 'ldap_attr_xxxx', 1, 0, 'var' ],
>>           [ 'UserXxxx', 'Xxxx', 'ldap_attr_xxxx', 1, 0, 'var' ],
>>           [ 'UserAddress', 'Address', 'postaladdress', 1, 0, 'var' ],
>>           [ 'UserComment', 'Comment', 'description', 1, 0, 'var' ],
>>       ],
>>   };
>>
>>  
>>> Neil
>>
>>  Martin
>>
>>--
>>((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg
>>         http://www.otrs.de/ :: Tel. +49 (0)6172 4832388
>>
>>_______________________________________________
>>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/ _______________________________________________
>>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/
>>
>
>
>DISCLAIMER:
>This message contains information that may be privileged or 
>confidential and is the property of the Roxar Group. It is 
>intended only for the person to whom it is addressed. If you 
>are not the intended recipient, you are not authorised to 
>read, print, retain, copy, disseminate, distribute, or use 
>this message or any part thereof. If you receive this message 
>in error, please notify the sender immediately and delete all 
>copies of this message.
>_______________________________________________
>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/
>_______________________________________________
>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/
>


DISCLAIMER:
This message contains information that may be privileged or confidential and is the 
property of the Roxar Group. It is intended only for the person to whom it is 
addressed. If you are not the intended recipient, you are not authorised to read, 
print, retain, copy, disseminate, distribute, or use this message or any part thereof. 
If you receive this message in error, please notify the sender immediately and delete 
all copies of this message.
_______________________________________________
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/
_______________________________________________
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