Authentication failed with MSSQL Server 2005

[tetiferr]

Hi,
I had installed OpenKM 5.0 on my server with microsoft sql server 2005.
After a long night spent to configurate all, the database table are been created and i have changed 2 of them I also CREATE TABLE OKM_PROFILE ...- I did all the other steps in wiki installation guide for mssql database.

Unfortunately, entering with okmAdmin / admin I get the message of authentication failure, then I opened Activity Monitor, and I watch that the last command was executed "(@ P0 nvarchar (4000)) as select usr_password PASSWD from OKM_USER usr_id WHERE = @ P0 and usr_active = 1"

The password in table OKM_USER is "21232f297a57a5a743894a0e4a801fc3" (admin)..


I do not know what to do, what I'm missing?

I hope in the help of a guardian angel ...

[jllort]

ensure your login configuration has

Code: Select all

<module-option name="hashAlgorithm">md5</module-option>
<module-option name="hashEncoding">hex</module-option>

try executing the two selects defined in login-config.xml

Code: Select all

select usr_password as PASSWD from OKM_USER where usr_id='okmAmin' and usr_active=1
select ur_role as ROLEID, 'Roles' from OKM_USER_ROLE where ur_user='okmAdmin'

The pass is encrypt whith md5 it's normall appears as is.

[pavila]

This sentence does return the list of active users?

Code: Select all

select * from OKM_USER where usr_active = 1

Boolean handling is not the same for each database, and not I don't remeber if this works for SQL Server.

[jllort]

To ensure problem is on authentication, login into http://localhot:8080/OpenKM/admin with that url we ensure that we're only testing authentication and nothing else about repository tables.

[tetiferr]

I have fixed the problem with the re-installetion and migrating to rel. 5.0.1 but it been very difficult

In first installation (5.0.0) was not created PRF_WZRD_PROPERTY_GROUPS and PRF_WZRD_WORKFLOWS fields in OKM_PROFILE Table and so I spent very much time to find this problem.

Thanks for your interest.

[pavila]

Yes, is a know issue but documented in wiki. We have fixed this in the development trunk.