Login problems after update

Hello,

we updated our RT from version 3.6.x to 4.0.0. all RT features works and
the new version is great :slight_smile: but one problem we have:

after the databasetransfer all users can login in RT. but when they logout
from RT and try another login, RT say, that the login credentials are
wrong. so we must update (update Users SET Password=md5(‘password’) where
Name=‘login’:wink: the credentials with mysql. than the user can login one
time again. when i look in the database, the md5 hashsum changed after
every login. so it is no wonder why the logins failed.
i checked the dependencies again and validated the database with
rt-validator, everything looks fine. have someone a tip for me to find the
problem?

thanks in advance

Tobias Nebel

IT-Systeme und Tools, VM-F11

IAV GmbH
Rockwellstrasse 16
38518 GIFHORN
GERMANY

Tel.: +49 5371 805 - 3611
Handy: +49 160 8944187

E-Mail: mailto:tobias.nebel@iav.de
Internet: http://www.iav.com

Sitz/Registered Office: Berlin,
Registergericht/Registration Court: Amtsgericht Charlottenburg,
Registernummer/Company Registration Number: HRB 21 280,
Geschäftsführer/Managing Directors: Kurt Blumenröder, Michael Schubert,
Dr. Rüdiger Goyk

we updated our RT from version 3.6.x to 4.0.0. all RT features works and the new version is
great :slight_smile: but one problem we have:

after the databasetransfer all users can login in RT. but when they logout from RT and try
another login, RT say, that the login credentials are wrong. so we must update (update Users
SET Password=md5(‘password’) where Name=‘login’:wink: the credentials with mysql. than the user
can login one time again. when i look in the database, the md5 hashsum changed after every
login. so it is no wonder why the logins failed.
i checked the dependencies again and validated the database with rt-validator, everything
looks fine. have someone a tip for me to find the problem?

Please show the output of SHOW CREATE TABLE Users;

-kevin

Hi

here is the output of SHOW CREATE TABLE Users;

mysql> SHOW CREATE TABLE Users;

| Table | Create Table |

| Users | CREATE TABLE Users (
id int(11) NOT NULL AUTO_INCREMENT,
Name varchar(200) NOT NULL,
Password varbinary(40) DEFAULT NULL,
Comments text,
Signature text,
EmailAddress varchar(120) CHARACTER SET ascii DEFAULT NULL,
FreeformContactInfo text,
Organization varchar(200) DEFAULT NULL,
RealName varchar(120) DEFAULT NULL,
NickName varchar(16) DEFAULT NULL,
Lang varchar(16) CHARACTER SET ascii DEFAULT NULL,
EmailEncoding varchar(16) CHARACTER SET ascii DEFAULT NULL,
WebEncoding varchar(16) CHARACTER SET ascii DEFAULT NULL,
ExternalContactInfoId varchar(100) DEFAULT NULL,
ContactInfoSystem varchar(30) DEFAULT NULL,
ExternalAuthId varchar(100) DEFAULT NULL,
AuthSystem varchar(30) DEFAULT NULL,
Gecos varchar(16) DEFAULT NULL,
HomePhone varchar(30) DEFAULT NULL,
WorkPhone varchar(30) DEFAULT NULL,
MobilePhone varchar(30) DEFAULT NULL,
PagerPhone varchar(30) DEFAULT NULL,
Address1 varchar(200) DEFAULT NULL,
Address2 varchar(200) DEFAULT NULL,
City varchar(100) DEFAULT NULL,
State varchar(100) DEFAULT NULL,
Zip varchar(16) DEFAULT NULL,
Country varchar(50) DEFAULT NULL,
Timezone varchar(50) CHARACTER SET ascii DEFAULT NULL,
PGPKey blob,
Creator int(11) NOT NULL DEFAULT ‘0’,
Created datetime DEFAULT NULL,
LastUpdatedBy int(11) NOT NULL DEFAULT ‘0’,
LastUpdated datetime DEFAULT NULL,
AuthToken varchar(16) CHARACTER SET ascii DEFAULT NULL,
PRIMARY KEY (id),
UNIQUE KEY Users1 (Name),
KEY Users4 (EmailAddress)
) ENGINE=InnoDB AUTO_INCREMENT=8053 DEFAULT CHARSET=utf8 |

1 row in set (0.02 sec)

mit freundlichen Grüßen
Tobias Nebel

IT-Systeme und Tools, VM-F11

IAV GmbH
Rockwellstrasse 16
38518 GIFHORN
GERMANY

Tel.: +49 5371 805 - 3611
Handy: +49 160 8944187

E-Mail: mailto:tobias.nebel@iav.de
Internet: http://www.iav.com

Sitz/Registered Office: Berlin,
Registergericht/Registration Court: Amtsgericht Charlottenburg,
Registernummer/Company Registration Number: HRB 21 280,
Geschäftsführer/Managing Directors: Kurt Blumenröder, Michael Schubert,
Dr. Rüdiger Goyk

Kevin Falcone falcone@bestpractical.com
Gesendet von: rt-users-bounces@lists.bestpractical.com
16.06.2011 14:42
Bitte antworten an
rt-users@lists.bestpractical.com

An
rt-users@lists.bestpractical.com
Kopie

Thema
Re: [rt-users] [RT4] login problems after update, Signatur Fehler

----- Nachricht von Kevin Falcone falcone@bestpractical.com auf Thu, 16
Jun 2011 08:42:15 -0400 -----
An:
rt-users@lists.bestpractical.com
Thema:
Re: [rt-users] [RT4] login problems after update

we updated our RT from version 3.6.x to 4.0.0. all RT features works
and the new version is
great :slight_smile: but one problem we have:

after the databasetransfer all users can login in RT. but when they
logout from RT and try
another login, RT say, that the login credentials are wrong. so we
must update (update Users
SET Password=md5(‘password’) where Name=‘login’:wink: the credentials
with mysql. than the user
can login one time again. when i look in the database, the md5
hashsum changed after every
login. so it is no wonder why the logins failed.
i checked the dependencies again and validated the database with
rt-validator, everything
looks fine. have someone a tip for me to find the problem?

Please show the output of SHOW CREATE TABLE Users;

-kevin

here is the output of SHOW CREATE TABLE Users;
Password varbinary(40) DEFAULT NULL,

You did not run the database upgrades between 3.6 and 4.0

Can you tell us what you did do?

You need to review all of docs/UPGRADING-3.6 3.8 and 4.0 and the README.
It appears that you’ve skipped all of the
rt-setup-database --action upgrade --dba root
steps and the standalone scripts.

-kevin