Dear Maxim and Openmeeting users, When I looked this attribute, I found it is a new attribute from OM 3.1,0. Furthemore, I used sAMAccountName as uid in my configuration file connected to AD.
In the latest version, should I need switch to userPrincipalName? I only have a test server installed OM 3.0.7. Thanks, Sent from Mail for Windows 10 刘文涛 Wentao Liu Partner of a cloud company Hunan Yun Zhong Man Bu Information Technology corp.Ltd 湖南云中漫步信息技术有限公司 Mobile phone: +86-13687359517 Fax: +86-731-88716009 From: Maxim Solodovnik Sent: 2016年4月11日 17:00 To: Openmeetings user-list Subject: Re: NULL login in om_users for new ldap users Great! Thanks for the update :) On Mon, Apr 11, 2016 at 2:49 PM, Oleg Palij <[email protected]> wrote: Maxim, sorry, I guess I lost this ldap_user_attr_login attribute during upgrade. After setting ldap_user_attr_login=userPrincipalName, it works as expected. 11 апр. 2016 г., в 10:44, Maxim Solodovnik <[email protected]> написал(а): 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. -- WBR Maxim aka solomax
