Authentication Error, version 4

[mc2301]

I have downloaded the bundle OpenKM 4, running it on Slackware 2.6.27.7-smp.
The shell script executes and I am able to connect OpenKM login screen with my browser on remote workstation.
However, I am unable to login neither with admin/admin, nor with okmAdmin credentials.
I have explored the forum and found some posts where editing of login-config.xml file mentioned.
However, there are no exact directives regarding the way to fix it.
Could anyone, please, share the correct file, or point to soem other possible cause of the above problem?
BTW, I am attempting to authenticate to OpenKM localy, no LDAP, no MySQL involved.

[mc2301]

Update: trying to login with okmAdmin and empty password leads to the following link:
http://myserver.org:8080/OpenKM/es.git. ... rity_check
which displays 404 NOT FOUND..

[jllort]

in your downloaded files there's some README.txt read it, there's explained that the actual user / password is:

user: okmAdmin
password: admin

Remember case sensitive !!!!

if don't works tell us,

[cnok]

My OpenKM 4.1 running on Win XP SP3 works fine for a week. It is during my pretest before releasing to users. However, computer was crashing due to electrical outage yesterday. When I reboot the server, everything seems to work fine. OpenKM can reboot as normal. But I cannot login. It always show Authentication Error message at the login screen. I have created several users already. I tried with all of them including okmAdmin account. Non of them work. I suspect that some file may need to recover. Any suggestion?

[cnok]

Hi,

Investigated further found that there is a file '.lock' with zero byte creted at /repository/.lock
After JBOSS is started and .lock is detected, there will be the following files created.
localDB.lck
OKMActivity.lck
OKMAuth.lck
OKMDashboardStats.lck
OKMWorkflow.lck

There was some message mentioning about repository shutdown improperly.

Can I just delete .lock and .lck ? Or need any process to recovery? My OpenKM and the repository is in a NAS and already contains approximately 20GB of documents.
Any suggestion?

[cnok]

Hi,

The problem has been resolved. I stopped Jboss and deleted all .lck files and .lock file then reboot the server. No Authentication Error problem anymore.

Regards,

[jllort]

.lck files indicate that database is locked ... you have killed the jboss process without normal jboss stop ? Be care with it, it's not good idea stop jboss while is still doing transactions, for some reason there a shutdown.bat script

[cnok]

No, It was not my intention to kill Jboss process. It was because of electrical failure.

By the way, in windows, when I run 'run.bat'. The DOS windows will remain open. Beside running shutdown.bat, press Ctl-C in JBOSS DOS window will also shut it down. What is the different? Should I always use 'shutdown.bat'?

[jllort]

It's the same.

You must evaluate the possibility to buy a UPS. Because with electrical faliures etc... you can easilly break the hard disk, mother board or simply corrumpt the repsitory ... bad idea not having one.