this was the behavior of old code
and I leave it "as is"
this is the example:
ldap_user_attr_phone=_bad_telephoneNumber
so you telling OM to get value of "totally" non-existent attribute
On 7 July 2014 21:11, Michael Wuttke
wrote:
> Hello Maxim,
>
> Sorry, but I didn’t get it!
>
> I don't wa
Hello Maxim,
Sorry, but I didn’t get it!
I don't want to store the the 'telephoneNumber'/'phone' in the OM db and
I don't want to store the 'description' (firstname & lastname) from
AD/LDAP in om.addresse.addtionalname which, is obviously in the OM GUI
the field of the street number.
How can I
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
wrote:
> Hello,
>
> If I am using OpenMeetings via LDAP as a normal user, two small issu
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'
/'add
