i got mod_vcard_ldap working the day after implementing ldap (AD) authentication. contact lists all displayed long drawn out usernames eg dt######@jabber.example.org. we abstract domain account names based on year of hire and employee number for security reasons. so no one had a clue who else was online. so before getting mod_vcard_ldap all nicely set up, i set local aliases (adium 1.0.2 client) for most users. then i found, with much chagrin, that mod_vcard_ldap could not affect the contact list name of a user. vcards looked great, but the list was still unintelligable. so i found and applied a patch implementing get_rosteritem_name() in mod_shared_roster.erl (required minor edit to use ldap over internal vcard).
Result: for most users, CN displays in the jabber client (yay!) (mostly gaim and adium). but for myself and others who locally set aliases during the day, those previously aliased users remain in the long usesless form. this behavior remained after wiping all application settings, cache, preferences and reinstalling. this behavior persists from machine to machine and various other clients. so local aliases, while not being pushed out to other users as might be useful, are actually not local and cannot be simply deleted through a client.
i'm guessing this data sits somewhere in /var/lib/ejabberd but i don't know which files can be cleared without breaking shared rosters and other company specific settings.
Any help appreciated. and happy to provide more info.
ps. aforementioned patch going to make it to ejabberd release ? original bug for this issue was opened in 2005. patch finally showed up late 2006... if i hadn't stumbled on this patch, i'd have no choice but to abandon ejabberd.
pps. shared roster managed via ldap would be highly desireable. and not a half-baked third party mod which is no longer even hosted for download. this is the last piece of the puzzle to a set-it-and-forget-it jabber server installation.
