LDAP Integration Module Config Issue

Hi Guys,

Firstly, I installed the module on Drupal 4.6.0 - it appears to talk OK to my the Unix accounts entries in my Openldap directory OK. Firstly, will upgrading Drupal to 4.6.3 make the module work any better?

Anyway, I can modify the selected LDAP entries fine. I am mapping the user's ldap uid attribute eg. mtrainer to the drupal login name and the ldap userPassword attribute to the Drupal password. My user entries in the LDAP directory (excluding lots of less important attributes) are in the form below:

dn: uid=mtrainer,ou=users,dc=xxxxxx,dc=net
uid: mtrainer
userPassword:: XXXXXXXXXXXXXXXXXXXXX
mail: mtrainer@xxxxxxxxxxxxxx
sn: Trainer
cn: Murray Trainer
mobile: 999 999 999
telephoneNumber: +999 9999 999
o: XXXXXXXXXX
ou:: XXXXXXXXXXXXXXXXX
userPassword:: XXXXXXXXXXXXXXXXXXXXX
sambaLMPassword: XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
sambaNTPassword: XXXXXXXXXXXXXXXXXXXXXXXXXXXX
uidNumber: 500
.
.

My problem is the Drupal Account Settings page under the My Account / Edit. I don't want user's to change their userid, password, or e-mail address via Drupal as that will break their e-mail client setup. Also their password is stored in 3 formats as shown below so changing them in the will put things out of sync. In anycase when I try to resave the entries retrieved for the user on the same screen it gives an error like the e-mail address already exists (or is already taken). Of course it does - it's mine? Unless my config is wrong, I will probably have to hack Drupal code to remove the fields I don't want edited :-(

I can probably live with the above and appreciate the work that has been done lately to get the module to this level of functionality that is useable. If in the future, full integration of Drupal users with LDAP is desired, a Drupal LDAP schema would need to be created to allow any Drupal user preference attributes that aren't already covered by standard LDAP schemas (such as default Drupal theme) to be stored in an LDAP directory. The schema part is pretty easy but not knowing much about the internals of Drupal, this may be hard to make work cleanly. It seems to me though that things are almost there already the way the module works at the moment.

Regards

Murray