Page 1 of 1

Can't force unlock (okm-002009) - not even the owner can

PostPosted:Mon Mar 19, 2012 1:11 pm
by Catscratch
Hi,

I've got the following problem. A user locked a document. But even the okmroot user can't unlock it. Not even the user itself can unlock it. There could be something wrong with the ldap configuration.

The detailed problem is described here:
http://issues.openkm.com/view.php?id=1627

Can you please help me an tell me why I can't unlock this document?

Thank you.

Re: Can't force unlock (okm-002009) - not even the owner can

PostPosted:Thu Mar 22, 2012 7:42 am
by jllort
Type the exact username appearing in document properties which lock the document and the user which are you logged, pay attention with upper case and lowercase.

Finally okmAdmin user can unlock any document

Re: Can't force unlock (okm-002009) - not even the owner can

PostPosted:Thu Mar 22, 2012 2:49 pm
by Catscratch
loginlowercase is on.

Re: Can't force unlock (okm-002009) - not even the owner can

PostPosted:Fri Mar 23, 2012 6:37 pm
by jllort
okmAdmin user can not unlock the file ?

put here the error in server.log while you are trying to unlock

Re: Can't force unlock (okm-002009) - not even the owner can

PostPosted:Fri Mar 23, 2012 9:33 pm
by Catscratch
The server log is in the bugtracker:
http://issues.openkm.com/file_download. ... 3&type=bug

Re: Can't force unlock (okm-002009) - not even the owner can

PostPosted:Sun Mar 25, 2012 1:28 pm
by pavila
I have made some improvement in the role check routine. Please, try wi the last night build.

Re: Can't force unlock (okm-002009) - not even the owner can

PostPosted:Tue Mar 27, 2012 2:26 pm
by Catscratch
I tried it in our testsystem and it works. :-)

What did you changed?

Re: Can't force unlock (okm-002009) - not even the owner can

PostPosted:Sat Mar 31, 2012 8:02 am
by pavila
Nice :)

Re: Can't force unlock (okm-002009) - not even the owner can

PostPosted:Mon Apr 16, 2012 8:11 am
by Catscratch
Ok, I updated to integration build 7538.

My question is, wherefor is ldap.user and ldap.username used?
Code: Select all
principal.ldap.user.attribute = sAMAccountName
principal.ldap.user.search.base = ...
principal.ldap.user.search.filter = ...
principal.ldap.username.attribute = 
principal.ldap.username.search.base = 
principal.ldap.username.search.filter = 
I want to achieve the following.
In the Securitylist (e.g. on a folder) I want to see the users name (CN).

So, when I configure user.attribute to CN I see the users name. But then the security roles won't work, because it seems they are mapped to the loginname, not the users name. So I tried user.attribute as sAMAccountName and username.attribute as CN. But then I only the the logins in the security list. And users who log in, get the wrong label.
E.g. User1 logs in and in the bottom left corner the text "Logged in as User5" appears instead of "Logged in as User1".

So, how do I configure it in the right way?

Cross reference: http://forum.openkm.com/viewtopic.php?f=5&t=6196

Re: Can't force unlock (okm-002009) - not even the owner can

PostPosted:Tue Apr 17, 2012 11:30 am
by pavila
Don't mix questions in the same forum thread. Please open a new one.