Hi Wiktor, On Fri, Nov 29, 2002 at 04:24:32PM +0100, Wiktor Wodecki wrote:
Martin Edenhofer wrote:
Ja, because OTRS is working with database id references. If you would delete a user (or queue, ...) from the database, your delete the reference info. Important infos like owner or queue.
Stefan Wintermeyer wrote:
You don't wanna delete a user in the OTRS. Because he/she could have created or changed tickets. So you need the user for the history. What you can do is to disable the user. But you can not delete him/her.
okay, I understand the problem. What if we move it none theless to the LDAP and create a DB entry on-delete. This would save all references and give us the benefit of LDAP. What I would like to do is to make otrs completely independant from it's db user auth.
I know what you want! :)
what do you think about this approach?
I think this should be the way. But unfortunately it's a lot of work (need to rework/check all functions where user are used). -=> The "fastest" solution would be a sync-script "LDAP -> OTRS user table". What Do you think?
Wiktor Wodecki
Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- "Security is a process, not a product." - Bruce Schneider