Hi
We started using external auth for ldap auth using
RT::Authen::ExternalAuth on RT 3.8.2 for more than a month.
Our company name changed, so the email domain name changed from
foo.com to bar.com
I have user with valid account
1893818 muser User, My my.u...@foo.com
But he
On Wed, Jul 25, 2012 at 02:27:00PM -0400, Asif Iqbal wrote:
Hi
We started using external auth for ldap auth using
RT::Authen::ExternalAuth on RT 3.8.2 for more than a month.
Our company name changed, so the email domain name changed from
foo.com to bar.com
I have user with valid
On Wed, Jul 25, 2012 at 2:59 PM, k...@rice.edu k...@rice.edu wrote:
On Wed, Jul 25, 2012 at 02:27:00PM -0400, Asif Iqbal wrote:
Hi
We started using external auth for ldap auth using
RT::Authen::ExternalAuth on RT 3.8.2 for more than a month.
Our company name changed, so the email domain
On 07/25/2012 11:27 AM, Asif Iqbal wrote:
Should I change the matching restriction on the config file from
# to just the Name and EmailAddress to save
encountering problems later.
'attr_match_list'= [ 'Name',
On Wed, Jul 25, 2012 at 3:14 PM, Thomas Sibley t...@bestpractical.com wrote:
On 07/25/2012 11:27 AM, Asif Iqbal wrote:
Should I change the matching restriction on the config file from
# to just the Name and EmailAddress to save
encountering problems later.
On Wed, Jul 25, 2012 at 12:31:48PM -0700, Thomas Sibley wrote:
On 07/25/2012 12:26 PM, k...@rice.edu wrote:
# We cannot assume uniqueness of Name for global RT use. ktm - 20091104
# #SANITY CHECK THE NAME AND ABORT IF IT'S TAKEN
# if ($RT::SystemUser) { #This only works if