Well as a noob to the product and to perl, If you followed the directions in the wiki and it’s installed properly.
The first “error” I ran into this problem yesterday.
For me it was basically because the user’s email already existed as a “user”. To work around that I went to Configuration → Users and then searched for that email, selected the user set it so they could be assigned privileges . Then set the username to the uid for the user. At which point I guess you could remove the ability for them to be assigned privileges again (and they’d disappear off the user list again). That all said I don’t consider this a solution, because most users first experience will be sending an email, which will then stop them from logging into the website to track progress unless there is some support intervention. And importing the users everyday out of ldap is a task I will forget to do.
The second “error” however suggests the LDAP auth failed any ways.
The “third” error is just the generic error if anything went wrong.
“Dummy cerberus” email@example.com 13/09/2007 8:02 pm >>>
I have follow the Wiki page about configuring LDAP to authenticate my
users (ExternalAuthentication - Request Tracker Wiki)… I think that
authentication is working, but I cannot login with my users… I
cannot find out the problem… but the error messages is this one:
Sep 13 21:40:52 ironman RT: Transaction->Create couldn’t, as you
didn’t specify an object type and id (/opt/rt3/lib/RT/Record.pm:1466)
Sep 13 21:40:52 ironman RT: RT::User::IsLDAPPassword AUTH FAILED:
Sep 13 21:40:52 ironman RT: FAILED LOGIN for maripmar from
Thanks in advance and best regards
Community help: http://wiki.bestpractical.com
Commercial support: firstname.lastname@example.org
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
This incoming e-mail has been scanned by Nudgee College’s
installation of NetIQ’s MailMarshal.
Any attachments should be checked for viruses by you prior to
opening. St Joseph’s Nudgee College accepts no responsibility for
any harm caused by an attachment.
This email and any attached files are intended solely for the
addressee(s). If you received this email in error, please advise
us by return email.