I want to write small script to create about 100 logins,
but I have no idea how i could get them intop the database.
Is an entry in the mysql table enough?
bye sven
Sven Sternberger Tel.: +49 (0) 40 8998 4397
Desy Email: sven.sternberger@desy.de
Notkestr. 85
D-22607 Hamburg
I want to write small script to create about 100 logins,
but I have no idea how i could get them intop the database.
Is an entry in the mysql table enough?
I want to write small script to create about 100 logins,
but I have no idea how i could get them intop the database.
Is an entry in the mysql table enough?
Hello Ian,
this script seems to be the last missing brick in building the foundation for
a complete integration of RT into an existing LDAP structure (along with the
formaidable LDAP External User Lookup, the LDAPsync script from SCA and the
Qsearch add on). Unfortunately, I cannot get it to work from scratch, and it
does not come with any dosumentation other than the source.
I changed most of the filter stuff for the LDAP access except for the lines
Am I right in assuming that empoyeeNumber is part of Your ldap schema? Is this
Your primary key? If yes, is it safe to change it to our primary key? Does the
script expect any arguments?
Am I right in assuming that empoyeeNumber is part of Your ldap schema?
Is this Your primary key? If yes, is it safe to change it to our
primary key? Does the script expect any arguments?
Yes, employeeNumber is an attribute we have for separating people
actually working here with ones in the LDAP database for other
purposes (webhosting, CVS access et c). It should be portable
enough. The script doesn’t expect any arguments (it just loops through
all posixAccount’s, looks at the employeeNumber attribute, sees that
one’s there and pushes to the users-stack)
It’s fugly code that I slapped together by looking at the `rt’ script
provided and reading some Net::LDAP code, but it works. I forgot to
license it, so I have no idea if it’s BSD or GPL. Just give me some
credit in it and I’ll be happy.