i'm afraid i't not an issue Currently if attribute mapping is absent the default mapping is used Maybe you can use sort of "bad" mapping for your config .... not sure :(
On 7 July 2014 19:19, Michael Wuttke <[email protected]> wrote: > Hello, > > If I am using OpenMeetings via LDAP as a normal user, two small issues > occurred during the process of data sync/mapping. Only three attributes > should be mapped to the OM database: lastname/sn, firstname/givenName & > mail/mail. But 'description' from AD/LDAP is mapped to 'street number' > /'additionalname' in the OM db and 'telephoneNumber' is mapped to phone > (correctly), but should not be mapped, according to my ldap config file. > > My om_ldap.cfg looks like this: > # Ldap user attributes mapping > ldap_user_attr_lastname=sn > ldap_user_attr_firstname=givenName > ldap_user_attr_mail=mail > #ldap_user_attr_street=streetAddress > #ldap_user_attr_additionalname=description > #ldap_user_attr_fax=facsimileTelephoneNumber > #ldap_user_attr_zip=postalCode > #ldap_user_attr_country=co > #ldap_user_attr_town=l > #ldap_user_attr_phone=telephoneNumber > > Thanks for help, > Michael > -- WBR Maxim aka solomax
