Martin, I am not sure whether I am responding to your answer in the correct way so I could be opening up a new thread this way. If that's the case, sorry.
Thanks for your prompt response. I see that redirecting OTRS to my own customer table shouldn't be too much of a problem as long as I store the data into one table. However, for the agents it is a different story. I had a look into the modules for CustomerUser and User and am thinking along the following path: If I follow the same scheme as for CustomerUser I could add a load of a User DB module in Kernel::System::User. If I then take a copy of Kernel::System::CustomerUser::DB and adapt it to my needs (pointing to my own user table, mapping field names and values, etc.) I would have created my own user backend or am I thinking too simple? One other thing I am not sure of yet is whether I need to adapt Kernel::System::Auth::DB and maybe I am missing out others as well. I would be very grateful if you can advise me on this and I would, of course, be perfectly happy to share the code with you when I get it working. Thanks for your time. Kind regards, Tom Hesp Lage Maten 1 3828 TC Hoogland 033 4561723 / 06 53895236 [EMAIL PROTECTED] _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/
