I have dig into the code myself and found the problem is due to change in user password authentication scheme is changed.
‘users.password’ field is outdated and ‘users_secure.password’ & ‘users_secure.salt’ are used for login by clients using a web-browser.
So, I updated ‘login.php’ file for REST api login.
My question is , Is anybody already working on this issue? And if not where can I contribute my-patch as I have found 3 projects going on REST API.
I have medmasterpro’s email somewhere in my box, so we can also email them to see if they are working on this ( send me an email to brady@sparmy.com ) also in case they miss this post.
This has been a huge code review, which is taking a long time (due to minimal resources of OpenEMR; medmasterpro has been great and is usually very fast to respond). Will be nice to get another developer involved to help move this project along.
I have added a simple function to allow validation of user id and password with the new password/salting scheme. This function will allow confirmation of password in other scenarios as well. (such as verification of password when "locking’ a note).
Just sent an email to Medmaster Pro folks and cc’s you on it. To get code into that repo, suggest placing it on your github repo in a separate branch and then doing a pull request on github: http://help.github.com/articles/using-pull-requests
Hi Bikash,
I have the same issue with login.
Can you please tell me how to use your this patch for logging in to openemr.
I unable to find any helpful answers on the forum even.