John McCoy wrote: > Good points Mike, I did not think about the fact that future users can > still get added as [EMAIL PROTECTED] if they first are just a requester, this > would mean I either need a constant process to "fix" these or as you > suggest: > >> Since ExternalAuth has been refactored, I could add an Overlay to have >> ExternalAuth checked for info when a user is auto-created by e-mail and >> have the info loaded then. It wouldn't help past users, but would help >> future users that start by e-mail and then login. >> > I am thinking this might be best, I have a few more days before my next > major project kicks off, meaning I have some time to give back to RT. > Would you like to do this as part of LDAP.pm or externally? Give me some > guide lines and I will see what I can come up with.
Having thought about this (and had some sleep) since.. I realised that, as far as I know, ExternalAuth *already* looks up external user info when a user is autocreated by email because when the user is created CanonicalizeUserInfo is called which is overridden by ExternalAuth and so goes off to find the users info based on their email address.. Can you confirm this? -- Kind Regards, __________________________________________________ Mike Peachey, IT Tel: +44 114 281 2655 Fax: +44 114 281 2951 Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK Comp Reg No: 3191371 - Registered In England http://www.jennic.com __________________________________________________ _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
