Import users

I would like to import existing users within our Active Server
Directory into Request Tracker. Once there I will then authenticate
from Apache. I found this great link (http://www.gossamer-
threads.com/lists/rt/users/17084?search_string=ldap%20user;#17084)
with a tar attachment (rtimportldap.tar) that does just the thing but
it’s now more than three years old. Is it still valid or has
something else come along to replace it?

Thanks!

Why not jsut authenticate against the ADS server live?

Dave Surmon wrote:

because I want users and their information within RT and I need them
within RT before the creation of tickets.On Feb 13, 2006, at 12:33 PM, Jason Fenner wrote:

Why not jsut authenticate against the ADS server live?

Dave Surmon wrote:

I would like to import existing users within our Active Server
Directory into Request Tracker. Once there I will then
authenticate from Apache. I found this great link (http://
www.gossamer- threads.com/lists/rt/users/17084?search_string=ldap%
20user;#17084) with a tar attachment (rtimportldap.tar) that does
just the thing but it’s now more than three years old. Is it
still valid or has something else come along to replace it?

Thanks!


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Download a free sample chapter of RT Essentials from O’Reilly
Media at http://rtbook.bestpractical.com

WE’RE COMING TO YOUR TOWN SOON - RT Training in Amsterdam, Boston and
San Francisco - Find out more at http://bestpractical.com/services/
training.html

This would do that for you, wouldn’t it?

http://blank.org/memory/output/rt-ad-sso.html

Dave Surmon wrote:

It only partially does it. I need a script that creates a batch of
users from my ldap directory server.On Feb 13, 2006, at 12:54 PM, Jason Fenner wrote:

This would do that for you, wouldn’t it?

http://blank.org/memory/output/rt-ad-sso.html

Dave Surmon wrote:

because I want users and their information within RT and I need
them within RT before the creation of tickets.

On Feb 13, 2006, at 12:33 PM, Jason Fenner wrote:

Why not jsut authenticate against the ADS server live?

Dave Surmon wrote:

I would like to import existing users within our Active Server
Directory into Request Tracker. Once there I will then
authenticate from Apache. I found this great link (http://
www.gossamer- threads.com/lists/rt/users/17084?search_string=ldap
% 20user;#17084) with a tar attachment (rtimportldap.tar) that
does just the thing but it’s now more than three years old.
Is it still valid or has something else come along to replace it?

Thanks!


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Download a free sample chapter of RT Essentials from O’Reilly
Media at http://rtbook.bestpractical.com

WE’RE COMING TO YOUR TOWN SOON - RT Training in Amsterdam,
Boston and
San Francisco - Find out more at http://bestpractical.com/
services/ training.html

It only partially does it. I need a script that creates a batch of
users from my ldap directory server.

I don’t know if it would help, but I had a similar situation,
where I wanted to coordinate my RT users with real users
that I have in ldap and sql, etc.

So I hacked a little, to get the following:

1. We use web external auth, so the passwords
   are always just stored in ldap.

2. If someone logs into the web site or sends email,
   and doesn't already have an RT account, it
   creates one on the fly.  However, I made sure
   all auto-created accounts (web or email) are non-privileged.
   Giving a consultant privs is a manual thing :-)

3. When an account is autocreated, I can sometimes identify
   the person by the web login or cannonicalize the email address.
   If so, then I do a (ph in my case, ldap in yours) lookup
   of additional info (dept name, phone) and stick these
   into RT during acct creation.

Everything happens in the right order, and tickets do get
created correctly first time.

Only minor issue, I don't have a good way to delete people
when they leave, but Jesse and Todd have pointed me in
some very promising directions, so I have to go read some more code
when I next come up for air.

(I don't think I submitted all the changes back to BP, since they
didn't seem to be of enough generality at the time; they were
really set up for my specific case.  But the overall
idea shouldn't be all that hard to copy.  Now, it would be real
cool if I could store some url, maybe with ldap: protocol,
in RT and have it lookup the dept, phone etc in real time. My scheme
above is static, accurate only at the acct creation time.
But, that's beyond what I need/have time for.)

I could probably dig up where I made my changes, if that helps.

    bobg
idea shouldn't be all that hard to copy.  Now, it would be real
cool if I could store some url, maybe with ldap: protocol,
in RT and have it lookup the dept, phone etc in real time. My scheme
above is static, accurate only at the acct creation time.
But, that's beyond what I need/have time for.)

Have a look at what 3.6.0pre0 /3.4.CH7(Chaldea) has for on-the-fly
content inclusion for custom field values.

Jesse

idea shouldn't be all that hard to copy.  Now, it would be real
cool if I could store some url, maybe with ldap: protocol,
in RT and have it lookup the dept, phone etc in real time. My scheme
above is static, accurate only at the acct creation time.
But, that's beyond what I need/have time for.)

Have a look at what 3.6.0pre0 /3.4.CH7(Chaldea) has for on-the-fly
content inclusion for custom field values.

Jesse

It’s been said before, but nonetheless: You Guys Rock!
bobg