Hello Phil,
It is probably going to be easier for us to assemble this data for each customer, and directly update the OTRS database ‘customer_user’ table, than it is for us to write the fields into our eDir schema and then synchronise this with OTRS’s tables.
Actually you don't need to snychronize your LDAP to your OTRS database. OTRS is able to retrieve the customer data directly from the LDAP (and may cache this data to increase performance if you like). However, since LDAP can be used in far more applications than OTRS, I'd recommend using the LDAP for storing customer data. At least you have only one data source which needs to be updated.
Given that we have a full Customer record in the customer_user table, is it possible for OTRS just to use LDAP for the purpose of customer authentication only, without us having to modify our eDir entries at all?
Yes, OTRS differentiate between customer data backend and customer authentication backend. Thus, you can use your LDAP for authentication and retrieve the customers data from your OTRS- or any other accessible database.
Also, if we have Customer data in ‘customer_user’ and are just using LDAP for Customer (and User/Agent) authentication, will we be able to edit individual users via the OTRS web interface? I assume there would be no reason why we couldn’t also edit the ‘customer_user’ table directly if we preferred.
Also an agreement on this point. If you have the corresponding permissions, you may update a customer users data in die OTRS-database. If you are using a writable LDAP-backend (currently not available in default OTRS installations but possible) you may also update your customer users data directly in the LDAP. kind regards, Torsten Thau -- ** Besuchen Sie uns auf dem LinuxTag in Berlin ** ** vom 9. - 12. Juni, Stand 110 in Halle 7.2A** Torsten Thau, Dipl. Inform. c.a.p.e. IT Labs GbR - Annaberger Str. 240 - D-09125 Chemnitz phone: +49 371 5347 623 cell: +49 176 66 680 680 personal pgp-key: 0x93E0A174 fax: +49 371 5347 625 http://www.cape-it.de