Discussion:
[otrs] OTRS 2.3.1 Upgrade Login Issue
David Salson
2008-08-21 18:26:15 UTC
Permalink
To All,

Upgrade from 2.2.7 to 2.3.1. Everything is running (cron, autoreply,
notifications, etc...) but no one can login (index.pl or customer.pl).
Invalid user name or password. I checked the database via phpMyAdmin. All
users are there. What to do?

Thanks,
Wes Plate
2008-10-22 22:02:32 UTC
Permalink
Post by David Salson
Upgrade from 2.2.7 to 2.3.1. Everything is running (cron, autoreply,
notifications, etc...) but no one can login (index.pl or customer.pl).
Invalid user name or password. I checked the database via phpMyAdmin. All
users are there. What to do?
Did you ever find the solution to your password problem? I'm seeing
something similar.

Users with passwords in the database from before the upgrade from 1.3 to
2.3.3 can log in, however new users or old users with new passwords cannot
log in.
--
Wes Plate
Automatic Duck, Inc.
http://www.automaticduck.com
Michael Webber
2008-10-22 22:58:00 UTC
Permalink
Out of curiosity, did you run the following scripts:

After upgrade:

### $OTRS_HOME is usually /opt/otrs ###

MYSQL:
cat $OTRS_HOME/scripts/DBUpdate-to-2.3.mysql.sql | mysql -p -f -u root
otrs

PostgreSQL:
cat $OTRS_HOME/scripts/DBUpdate-to-2.3.postgresql.sql | psql otrs

Then:

$OTRS_HOME/scripts/DBUpdate-to-2.3.pl


Then:

MySQL:
cat $OTRS_HOME/scripts/DBUpdate-to-2.3-post.mysql.sql | mysql -p -f -u
root otrs
PostgreSQL:
cat $OTRS_HOME/scripts/DBUpdate-to-2.3-post.postgresql.sql | psql otrs

Login as ***@localhost (default password is root) and verify if changes
took effect.


-----Original Message-----
From: otrs-***@otrs.org [mailto:otrs-***@otrs.org] On Behalf Of
Wes Plate
Sent: Wednesday, October 22, 2008 3:03 PM
To: OTRS; David Salson
Subject: Re: [otrs] OTRS 2.3.1 Upgrade Login Issue
Post by David Salson
Upgrade from 2.2.7 to 2.3.1. Everything is running (cron, autoreply,
notifications, etc...) but no one can login (index.pl or customer.pl).
Invalid user name or password. I checked the database via phpMyAdmin. All
users are there. What to do?
Did you ever find the solution to your password problem? I'm seeing
something similar.

Users with passwords in the database from before the upgrade from 1.3 to
2.3.3 can log in, however new users or old users with new passwords
cannot
log in.
--
Wes Plate
Automatic Duck, Inc.
http://www.automaticduck.com


_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Michael Webber
2008-10-22 23:00:15 UTC
Permalink
One other thing, did you run the http://localhost/otrs/installer.pl and
create a different database?

-----Original Message-----
From: otrs-***@otrs.org [mailto:otrs-***@otrs.org] On Behalf Of
Wes Plate
Sent: Wednesday, October 22, 2008 3:03 PM
To: OTRS; David Salson
Subject: Re: [otrs] OTRS 2.3.1 Upgrade Login Issue
Post by David Salson
Upgrade from 2.2.7 to 2.3.1. Everything is running (cron, autoreply,
notifications, etc...) but no one can login (index.pl or customer.pl).
Invalid user name or password. I checked the database via phpMyAdmin. All
users are there. What to do?
Did you ever find the solution to your password problem? I'm seeing
something similar.

Users with passwords in the database from before the upgrade from 1.3 to
2.3.3 can log in, however new users or old users with new passwords
cannot
log in.
--
Wes Plate
Automatic Duck, Inc.
http://www.automaticduck.com


_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Wes Plate
2008-10-22 23:04:12 UTC
Permalink
Post by Michael Webber
One other thing, did you run the http://localhost/otrs/installer.pl and
create a different database?
I did, but then I changed the database that OTRS was using to the one I
upgraded from the old system. I changed Config.pm to use the database I'm
calling "otrs2" instead of "otrs".
--
Wes Plate
Automatic Duck, Inc.
http://www.automaticduck.com
Michael Webber
2008-10-23 02:32:30 UTC
Permalink
Try changing it back to "otrs" and then login. I just had this same issue when I was upgrading earlier tody.

Since I ran the scripts and changed the Config.pm back to "otrs" everything worked and all of my info was still there.

Let me know if this works for you.

-----Original Message-----
From: Wes Plate <***@automaticduck.com>
Sent: Wednesday, October 22, 2008 4:38 PM
To: OTRS <***@otrs.org>
Subject: Re: [otrs] OTRS 2.3.1 Upgrade Login Issue
Post by Michael Webber
One other thing, did you run the http://localhost/otrs/installer.pl and
create a different database?
I did, but then I changed the database that OTRS was using to the one I
upgraded from the old system. I changed Config.pm to use the database I'm
calling "otrs2" instead of "otrs".
--
Wes Plate
Automatic Duck, Inc.
http://www.automaticduck.com


_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Wes Plate
2008-10-23 15:01:23 UTC
Permalink
Post by Michael Webber
Try changing it back to "otrs" and then login. I just had this same issue
when I was upgrading earlier tody.
Since I ran the scripts and changed the Config.pm back to "otrs" everything
worked and all of my info was still there.
Let me know if this works for you.
I CAN create new users and log in using the new "otrs" database created by
2.3.3's installer.pl script. However that doesn't do me any good since I
need to use my old database that I'm trying to migrate.

I was imagining there is a setting in the database that tells OTRS how to
encrypt/decrypt the password and that the encrypt/decrypt methods were not
in sync for the old database and new users to that old database.

Our wonderful OTRS consultant is going to look at our system later today, I
was hoping to research a solution to this problem for him.
--
Wes Plate
Automatic Duck, Inc.
http://www.automaticduck.com
Wes Plate
2008-10-22 23:02:40 UTC
Permalink
Yeah, the database was upgraded from 1.3 to 2.0 then to 2.1 then to 2.2 then
to 2.3 and the 2.3 step was done with its three parts.
--
Wes Plate
Automatic Duck, Inc.
http://www.automaticduck.com
Loading...