What we're trying to do is avoid adding user info when ticket requests come in. We have a very large user base (~1500 different users) that will be using either a web form or email to submit tickets. We have an on campus ldap server that has everyone's information, and we would like the system to query the ldap server whenever a ticket comes in for the address and phone number. We were thinking that a scrip would be the easiest, since the tickets will be coming from two different sources (email and web form), but other options would be considered. Any suggestions?
Thanks! ~George Message: 5 Date: Sun, 18 Jun 2006 21:58:10 -0700 From: "Jim Meyer" <[EMAIL PROTECTED]> Subject: Re: [rt-users] LDAP Custom action To: "George Bishop" <[EMAIL PROTECTED]> Cc: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hello! On 6/18/06, George Bishop <[EMAIL PROTECTED]> wrote: > Does anyone have experience with writing custom actions with LDAP? I'm > beginning to write a custom action to query a ldap server to get > specific information on requesters when they send a help request. Is it > ok to have "use Net::LDAP" in such an action, or does this need to be > put elsewhere? Thanks in advance for any help. Assuming that you've already looked at the LDAP auth/info overlay (http://wiki.bestpractical.com/?LDAP), then I don't have a lot more to offer. However, I'm curious what sort of info and whether it could be mapped into the RT account's "Extra Info" field, then just looked up internal to RT rather than externally. That would also make the info easily available to scrip actions. Cheers! --j -- Jim Meyer, Geek at Large [EMAIL PROTECTED] _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com We're hiring! Come hack Perl for Best Practical: http://bestpractical.com/about/jobs.html
