Login v.4.2 problems

omo66 wrote on Friday, May 01, 2015:

I upgraded oemr 4.1 to 4.2 and moved files to a new ubntu-13 box V4.2 php5263 it works fine in production so far.
From the new server I created using mysqldump and rsync backup copy of production (v4.2) on ubuntu-8 php5531 within same network box.
i cann’t login on ubuntu-8 (Invalid username or password) to the exact copy-demo
DOES V4.2 HAS SECURITY FEATURES PREVENTING ME LOGINING IN on different box?
THANKS

yehster wrote on Friday, May 01, 2015:

No. There were no changes in the login mechanisms between 4.1 and 4.2.

Also the description events of implies that a 4.2 copy (“works fine in production”), but the problem happened after migration. Seems most likely that the issue is with the migration itself or with the setup of the new box.

fsgl wrote on Friday, May 01, 2015:

A number of users, who transferred an old database, have had difficulties logging in to OpenEMR when the old credentials in sqlconf.php were used.

Try the credentials of the new database created in the second box.

yehster wrote on Friday, May 01, 2015:

Mod up for fsgl’s comment.

More details on which “login” is failing (OpenEMR user vs. database), would be helpful in diagnosing the problem.

omo66 wrote on Friday, May 01, 2015:

thanks all
I tested all users admin… no luck
The dumped db has same tables for users and same encrypted text
sql.conf.php is not edited since the backup box has same MYSQL credentials and it is querying and reading the backup DB showing (Invalid username or password)
IT MUST BE MD5() ISSUES MAKING PASSWORDS LOOKS DIFFERENTLY ??

fsgl wrote on Friday, May 01, 2015:

Usually the password in sqlconf.php (for the database) is not encrypted, while the passwords in the users_secure (for OpenEMR login) are.

Perhaps an example will help clarify the matter.

In the Windows Package, the username is openemr, while the password is escargot in sqlconf.php. If a user had OpenEMR installed previously in Ubuntu, but wishes to use the Windows Package in a new device, the user cannot use the sqlconf.php credentials from the Ubuntu copy. He must use openemr/escargot.

I don’t fully understand the “mechanics” for this phenomenon, but this is an empirical observation of a number of users, who were only able to login to OpenEMR, following an upgrade or transfer; with the credentials of the new database.

Fortunately the downloads are not so big & fat that MD5 checksums are required. Have yet to come across posts questioning the fidelity of download transmissions in the past 3 years.

If this does not work, post error logs.

omo66 wrote on Friday, May 01, 2015:

I reseted admin password to ‘pass’ using phymyadmin
I was able to login and left navigation is white space only
I looks like permission or function() issues.
my install was from production downloaded file.
I inspected file left_nav.php and noticed first lines : see below:

see image THERE IS a ‘I’ ? before ‘<?php’ is this normal

yehster wrote on Friday, May 01, 2015:

OpenEMR migrated away from MD5 to SHA1 in 2011 as part of 4.0.0.

So the likelyhood that MD5 is the problem is low.

However what could be an issue is that one system has CRYPT_BLOWFISH and the other does not.

fsgl wrote on Saturday, May 02, 2015:

See this.

Henry had to upgrade Ubuntu.