Re: [dev] Some changes that i`ve make in OTRS

On Tuesday 22 June 2004 19:41, Robert Kehl wrote:

On Tuesday, June 22, 2004 9:50 AM

Dmitriy Borisov wrote:

...

I`d change source of OTRS for my needs. I think, that it can be useful for other. So, I posting it in this list.

Sorry, but could I get you to describe what the changes are doing, and provide a patch instead of the whole file(s)? Please use

# cd /opt/otrs # diff -bru Kernel/System/CustomerAuth/DB.pm.orig Kernel/System/CustomerAuth/DB.pm > DB.pm.patch

OK. I attach patch files to this letter. I`m working with OTRS version 1.1.3, but this patch describes difference between my patched version of OTRS and OTRS version 1.2.3 sources. In patch files some new things are disabled because of my old sources. My version of DB.pm is wrote because I got to only authenticate my customers with external database. And I think, that with this patch "New customer" and "Change customer password" features will not work correctly. Exactly, they must not work correctly :( May be in future I`ll add support of changing this options in other modules. In my version of OTRS all operations with CustomerPreferences and Customer authenticate options must be disabled because I have external interface to work. I`d disabled they by changing forms to hide this options from customer. This changes I`m not posting to you because it is simple and I think that only some peoples can have need for they. But I can to do it if it is important. Changes in Config.pm was wrote to provide future configure capability with other modules of OTRS. There are none difference with describing options for CustomerUser preferences of Config.pm.dist in Config.pm file. Changes in Kernel/System//CustomerAuth/DB.pm was wrote to provide authentication of my users with external database. There had changes made in SQL query to database (using parameters from Config.pm) and in new routine to import options from Config object to this CustomerAuth::DB object. Changes, that I was made, include an unencrypted password verification because passwords in my database are stored in unencrypted format. I think, that all changes that I make can be useful for users, that have own customer database and want to integrate OTRS system in there customer workspace. Again, sorry for my English, it isn`t my native language -- With best regards, Dmitriy Borisov Network administrator of INTS ISP Ukraine, Donetsk E-mail: borik@ints.net