On Wed, Sep 15, 2010 at 11:42:25AM +0200, Tom Sylwestrowicz wrote: > I know why this error is happening here, it's basically because the LDAP > e-mail address field defaults to [email protected]. Joe has an alias that > he uses, which is [email protected] which is also set up in his e-mail > client. So when he sends a request to the RT queue, his address is seen > as [email protected], which is not what's in LDAP. This is the default > e-mail setup we have here in the work place. > > We can add an alias ([email protected]) for his user ID in LDAP, but > is there a way that RT3 would check the aliases fields in LDAP and then > associate incoming requests from the [email protected] alias with the > default LDAP e-mail address of [email protected]?
I'm assuming you're using RT::Authen::ExternalAuth, but you don't say. That has been an outstanding request for that module which has not yet been implemented. -kevin
pgpcahDasin3a.pgp
Description: PGP signature
RT Training in Washington DC, USA on Oct 25 & 26 2010 Last one this year -- Learn how to get the most out of RT!
