[rt-users] Re: LookupSenderInExternalDatabase ?

[Bob Goldstein]

>"Bob Goldstein" <bobg at uic.edu> writes:
>
   ...
>
>If I went this route, I'd patch Create() to include a canonicalize
>function similar to the WebAuth ones. Though you could just have
>people's account names be their email addresses, and canonicalize the
>external auth to match. 

   No, I can't can't have people's account names be their
   email addresses. We already have a web auth system in
   use for many years with many apps, and was so trivially
   easy to hook into RT. (Sure, I could do a translate
   somewhere internally, but I want to display our normal
   names in RT as well, so that's the wrong solution.)

   You're right about Create() being a good place for this.
   But my problem is really a question of RT style:
   Create() is a big routine, and if I override it in
   User_Local.pm, I have to copy over the entire routine
   and change 2 lines.  What happens if, in the next release,
   Create() itself changes?  Then I have to notice and
   repatch my system.

   I'd prefer that Create(), itself, natively called
   some cannocicalize_email_to_name() funtion, which by default
   just returned its argument. Then I could override that,
   and be future-safe.

   Is there a third way?  I don't see it, but I'm very new
   to RT (only in the demo stage, about to pitch my boss that
   we ought to take a serious look), so maybe I'm overlooking
   something.

      bobg