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 tghesp@euronet.nl
Hi Tom, On Thu, Dec 04, 2003 at 01:51:01PM +0100, Tom Hesp wrote:
[...] 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
That's correct. .-)
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.
The Kernel::System::CustomerUser::XY module is for the customer data (name, email, ....). The Kernel::System::Auth::XY is for the authentication. So if you do have the customer passwords crypted in a SQL table, then you could use Kernel::System::Auth::DB. If you want to authentication you users aganins LDAP, use Kernel::System::Auth::LDAP. If you want your own authentication way then write your onw Kernel::System::Auth::XY. .-) I hope it helps you!
Tom Hesp Lage Maten 1 3828 TC Hoogland 033 4561723 / 06 53895236
Martin -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!
Hi Martin, Sounds pretty straight forward, thanks a lot. I will start to do some perl code hacking next week and see if I can get things running. Kind regards, Tom -----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org]On Behalf Of Martin Edenhofer Sent: donderdag 4 december 2003 21:55 To: User questions and discussions about OTRS. Subject: Re: [otrs] Integrating OTRS Hi Tom, On Thu, Dec 04, 2003 at 01:51:01PM +0100, Tom Hesp wrote:
[...] 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
That's correct. .-)
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.
The Kernel::System::CustomerUser::XY module is for the customer data (name, email, ....). The Kernel::System::Auth::XY is for the authentication. So if you do have the customer passwords crypted in a SQL table, then you could use Kernel::System::Auth::DB. If you want to authentication you users aganins LDAP, use Kernel::System::Auth::LDAP. If you want your own authentication way then write your onw Kernel::System::Auth::XY. .-) I hope it helps you!
Tom Hesp Lage Maten 1 3828 TC Hoogland 033 4561723 / 06 53895236
Martin -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication! _______________________________________________ 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/
participants (2)
-
Martin Edenhofer -
Tom Hesp