What do you mean by one identity? If you want to know if OpenKM can authenticate to another database, yes it can. I know for sure it can be set up to authenticate to an LDAP server.
I don't know if there's a reason for it, but why would a user log in more than once at a time?
One identity - something like anonymous account. Actually I want to avoid creating user account for every user as long as there is no webservice for this and it is not required for me to trace who is author of any file etc.
It is obvious this user account should be able to be logged in more than once.
Now it's not implemented the anonymous user. And other problem, than on future we'll solve is that one user only can be loged one time on OpenKM not twice ( that's a security issue that has become tedious, and we've planned to remove this restriction ).
So is it possible for me to solve it now - some hack?
Can I for example share SessionID of one user for more clients (I am using webservice) or just turn off authentication for webservice clients (and restrict access by firewall), etc...?