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.
~George
Hello!On 6/18/06, George Bishop bishopg@bu.edu 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
(Request Tracker Wiki), 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 purp@acm.org
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: 5Date: Sun, 18 Jun 2006 21:58:10 -0700
From: “Jim Meyer” purp@acm.org
Subject: Re: [rt-users] LDAP Custom action
To: “George Bishop” bishopg@bu.edu
Cc: rt-users@lists.bestpractical.com
Message-ID:
c09f2f8a0606182158m3e2e44casb9cdb5ec2cea15a7@mail.gmail.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hello!
Hello!On 6/20/06, bishopg@bu.edu bishopg@bu.edu wrote:
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?
Ah, I see now. You should really look at the LDAP Overlay
(Request Tracker Wiki) … it does exactly what you’re
asking via the $LdapAttrMap , where you can map any field in LDAP to a
corresponding attribute of the RT::User object. In your case, it
sounds like you want to map some things in LDAP to RT::User’s
Address1, Address2, and either WorkPhone or HomePhone attributes.
Cheers!
–j
Jim Meyer, Geek at Large purp@acm.org