Hello…
I cannot login to openemr after giving my login in info following the recent code changes. I am in Windows machine and using xampp…openemr version 4.1.2…developer version…
After putting my username and password…it just pops up a new window saying: Server Configuration Problem…
Fortunately, it looks like you are doing things in a test environment.
XAMPP and the latest code have a big problem that we are still trying to sort out.
Note the code is still in development phases, but would be great if you let me know if it works for you (ie. only use it on a disposable testing server).
As I posted on the above forum link, what we decide to code and this fix (if we use it) will likely take some time. So at this point, I’d consider our current development master branch very unstable.
Hi…just installed your branch and created a new testing openemr database with the branch code…the installation went fine…
I was able to login with username: admin and password pass
There is a problem with the add user window in the administration section
Whenever i try to add a user, by entering the username and the desired password and also the current admin password as needed by the new mechanism, and click on save button, nothing happens. There is just no processing of any kind
Even the patient portal is not working. I have tested only the onsite portal.
Hi Arnab,
Kevin resolved it by basically removing it. We decided to follow standard best practices and not do any encryption/hashing on the client/browser in OpenEMR and rely on SSL/HTTPS use.
-brady OpenEMR
But how to activate the ssl or https in windows…can u please help me with that…from openemr if I try to download the certificate from adminstation => certificates…it doesnot work…
Suggest googling for setting “SSL XAMPP” (I saw a couple good tutorials including a video, which I can copy/paste links here if you can’t find them) to see what needs to be done and recommend not using the Administration->Certificate module for now (once you get comfortable with certificates etc. then can think about client sides certificates).
This is something that we will need to document well on the wiki since we need to recommend users to use this in the future (note that not using http (and not https) is insecure unless connecting over localhost; ie. client/server are the some computer)). Let us know how it goes.