[rt-users] ExternalAuth, local users, and upgrade woes

[Izz Abdullah]

That is odd.  The migrate database should have set it to varchar(256), at least that is how our mysql database, imported 3.8.6 and upgraded to 4.0.2, is on the password field as well.  Did you have any errors on the migration sequence?

-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Yan Seiner
Sent: Wednesday, November 09, 2011 11:45 AM
To: rt-users at lists.bestpractical.com
Subject: Re: [rt-users] ExternalAuth, local users, and upgrade woes


On Wed, November 9, 2011 9:10 am, Kevin Falcone wrote:
> On Wed, Nov 09, 2011 at 09:01:01AM -0800, Yan Seiner wrote:
>>
>> On Wed, November 9, 2011 8:49 am, Kevin Falcone wrote:
>>
>> > If you're having trouble managing RT internal users while logged in as
>> > an LDAP user, please see Ruslan's response about possible bugs.  Try
>> > logging in as root and seeing if that helps.
>>
>> Is the bug report public?  If so, where?
>
> If there is an existing bug report it would be in the rt.cpan.org
> queue for RT-Authen-ExternalAuth.  If there is no report, please make
> one.

I've been poking around in the databases...

In the virgin RT4 database (the one we created from scratch) the password
field is varchar(256).

In the converted RT3->RT4 database the password field is varbinary(40).

In the original RT3 database, the password field is varbinary(40).

I don't know enough about mysql but that doesn't seem right.  Can some
mysql gurus clue me in?



-- 
Pain is temporary. It may last a minute, or an hour, or a day, or a year,
but eventually it will subside and something else will take its place. If
I quit, however, it lasts forever.

--------
RT Training Sessions (http://bestpractical.com/services/training.html)
*  Barcelona, Spain  November 28 & 29, 2011