Skip Menu |

This queue is for tickets about the RT-Authen-ExternalAuth CPAN distribution.

Report information
The Basics
Id: 59034
Status: resolved
Priority: 0/
Queue: RT-Authen-ExternalAuth

People
Owner: Nobody in particular
Requestors: hopkinsju [...] umsystem.edu
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Username lookups should be case insensitive
Date: Thu, 1 Jul 2010 15:35:27 -0500
To: "bug-RT-Authen-ExternalAuth [...] rt.cpan.org" <bug-RT-Authen-ExternalAuth [...] rt.cpan.org>
From: "Hopkins, Justin" <hopkinsju [...] umsystem.edu>
While using Authen-ExternalAuth I encountered a problem creating users or logging in when the capitalization of the username did not match the value stored in the external database. I am using RT 3.8.8 and External Auth 0.08, mysql5 - both RT and the external database are running on this server with ci collation. Performing a query by hand returns the desired results. This presents a problem because people seem to be fond of entering email addresses differently all over the place. One of the users in my database entered her email as Jane.Doe@gmail.com but has her email client configured to send as jane.doe@GMAIL.COM - This has resulted in myriad issues with RT. Users cannot be autocreated, created by hand, or created by adding them as a watcher. It *is* possible to update a user with a non-matching value. While you couldn't create a user like the one above by adding 'jane.doe@gmail.com' it is possible to add whatever is in the database with the same capitalization and then modify the existing user to be all lower-case. Regards, Justin Hopkins Coordinator, IT & Web Services MOBIUS Consortium Office c: 573-808-2309
Subject: Re: [rt.cpan.org #59034] Username lookups should be case insensitive
Date: Tue, 20 Jul 2010 16:17:20 -0500
To: "bug-RT-Authen-ExternalAuth [...] rt.cpan.org" <bug-RT-Authen-ExternalAuth [...] rt.cpan.org>
From: "Hopkins, Justin" <hopkinsju [...] umsystem.edu>
As a band-aid I've modified the MySQL table that external auth is checking to lowercase all values stored in the email column. This is a worthwhile temporary fix because most users tend to log in by typing their email addresses in lower case. Their *is* still a problem when users submit a ticket by email and the From: headers contain MyUser@example.com How is it nobody else has run into this problem? Cheers, Justin
On Tue Jul 20 17:17:34 2010, hopkinsju@umsystem.edu wrote: Show quoted text
> As a band-aid I've modified the MySQL table that external auth is > checking to lowercase all values stored in the email column. This > is a worthwhile temporary fix because most users tend to log in by > typing their email addresses in lower case. > > Their *is* still a problem when users submit a ticket by email and the > From: headers contain MyUser@example.com > > How is it nobody else has run into this problem?
I suspect most users of this extension are using the LDAP integration, not the DBI integration (Which was folded in from a separate module). There's be a change in behavior if we slapped an lc() into DBI.pm, but I'd take a patch to make that configurable. I'm also surprised that a mysql table is being case insensitive, since RT's internal tables certainly assume that mysql will treat GMAIL.COM and gmail.com the same. -kevin