We’re evaluating OTRS at present, and are looking to get LDAP authentication working. We’ve succeeded in getting Users (agents) authenticating against our LDAP server (eDir) but haven’t yet got Customer authentication working against this directory – we want our Customers to be able to login to the Customer web page with their eDir uids and passwords. Before we get too deeply into the mysteries of configuring this setup, can I just check one fundamental point - In our case, in order to provision each Customer record, we will need to be getting the fields from a number of different sources – our own MySQL tables, queries on a different LDAP server etc. 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. 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? This isn’t clear to me from the documentation. 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. This SEEMS to be the way things are working with our User/Agent LDAP authentication - I can see and edit agent details in the OTRS web interface, but any changes to password I put in there are ignored, and agents are correctly authenticated against my eDir login. Is this how it should work for customer users too, once we’ve sorted out the LDAP setup? I’d be grateful for any clarification on this point. Regards Phil Stanford