Can you check if ldap_user_attr_login attribute mapped correctly in your ldap.cfg file? I'll try to reproduce, fix this issue ASAP (I only have LDAP server available for testing)
On Mon, Apr 11, 2016 at 1:24 PM, Oleg Palij <[email protected]> wrote: > Hello! > > I'm on openmeetings 3.1.1 with users in ldap (active directory). > > When new ldap user loging in to openmeetings, it creates new record for > such user, but 'login' field for this user is empty. > When this user login again, openmeetings creates new record for this user > again, and again with empty 'login' field. > > When I fill 'login' manually after the first login it starts to work as > expected. > > https://monosnap.com/file/UYWTi3n7wYTK8MgBhr6CexYmaG3KEW > > mysql> select * from om_user where id=59\G > *************************** 1. row *************************** > id: 59 > activatehash: NULL > age: 2016-04-11 10:16:18 > deleted: > domain_id: 1 > external_id: NULL > external_type: NULL > firstname: NULL > forceTimeZoneCheck: > inserted: 2016-04-11 10:16:18 > language_id: 9 > lastlogin: NULL > lastname: operator > lasttrans: NULL > login: NULL > owner_id: NULL > password: NULL > pictureuri: NULL > regdate: 2016-04-11 10:16:18 > resethash: NULL > salutation: mr > sendSMS: > show_contact_data: > show_contact_data_to_contacts: > time_zone_id: Etc/GMT+2 > type: ldap > updated: NULL > user_offers: NULL > user_searchs: NULL > address_id: 59 > sip_user_id: NULL > > > -- WBR Maxim aka solomax
