LDAP Authentication & Retrieving User Information

Hi Everyone,

I have just read through the various Wiki documents concerning setting
up LDAP functionality within RT. There seems to be a conflict between
the AutoCreateAnd CanonicalizeUserInfor and LDAP WiKi documents. Both
suggest to install User_Local.pm in $RT_HOME/lib/RT. The LDAP version of
User_Local.pm authenticates users via LDAP; I want this. The
AutoCreate… User_Local.pm retrieves user information from LDAP when a
user account is created, I also want this. I know you cannot have two
User_Local.pm files in the same place, so is there a way to implement
both functionalities?

Thank you for your time.

Take care!

Nick

Hello!On Thu, 2005-12-15 at 08:51, Nick Metrowsky wrote:

I have just read through the various Wiki documents concerning setting
up LDAP functionality within RT. There seems to be a conflict between
the AutoCreateAnd CanonicalizeUserInfor and LDAP WiKi documents. Both
suggest to install User_Local.pm in $RT_HOME/lib/RT. The LDAP version
of User_Local.pm authenticates users via LDAP; I want this. The
AutoCreateпїЅ User_Local.pm retrieves user information from LDAP when a
user account is created, I also want this. I know you cannot have two
User_Local.pm files in the same place, so is there a way to implement
both functionalities?

Currently, LDAP authentication and LDAP information are implemented
separately; you’ll need to copy the functions from both pages into
your User_Local.pm in order to do both. This shouldn’t be tough, though,
as there are no naming conflicts.

Meanwhile, I’ve just finished an integration/refactor/update pulling all
of those together and implementing some new bits ($RT::AuthMethods to
specify which methods to use and in what order; $RT::LdapAttrMap as
suggested by Phillip Cole, author of the info implementation on the
AutoCreateAndCanonicalizeUserInfo page; and other bits).

I intend to post it on the LDAP page when I’ve got a moment, but that
won’t be for a week or so as I’m rolling it out today and will be
debugging and polishing further before it goes public.

Good luck!

–j
Jim Meyer, Geek at Large purp@acm.org