According to your post, I changed the config to: ldap_conn_host=192.168.x.x ldap_conn_port=389 ldap_conn_secure=false ldap_admin_dn=CN=ldapbind,CN=Users,DC=BLL,DC=local ldap_passwd=xxxxxxxxxxxx ldap_search_base=OU=Vlaamseoogpunten,DC=BLL,DC=local ldap_provisionning=AUTOCREATE ldap_deref_mode=always ldap_use_admin_to_get_attrs=true
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 ldap_use_lower_case=false ...but the result is the same, it doesn't work. How can I get more info about the specific error/problem ? There is no "ldap_server_type=AD" line anymore, is that correct ? Thanks, Ph. From: Maxim Solodovnik [mailto:solomax...@gmail.com] Sent: dinsdag 28 april 2015 13:59 To: Openmeetings user-list Subject: Re: LDAP not working anymore after upgrade to version 3.0.4 yes the format of the config has been changed please check the example here: https://svn.apache.org/repos/asf/openmeetings/branches/3.0.x/src/main/webapp/conf/om_ldap.cfg On Tue, Apr 28, 2015 at 5:45 PM, Philippe Dhont <dhont.phili...@vlaamsoogpunt.be> wrote: Hi, I upgraded to version 3.0.4 (from 3.0.1) and now login with our windows accounts (Active Directory) via LDAP doesn't work anymore. Configuration in OpenMeetings: LDAP config: Name: vloog Enabled > checked Config file name: om_ldap.cfg Add domain to user name > checked Domain: bll.local PREVIOUS OM_LDAP.CFG configuration when it worked with the previous OM version: ldap_server_type=AD ldap_conn_url=ldap://192.168.x.x:389 ldap_admin_dn=CN:openmeetingsLDAPuser,CN:Users,DC:BLL,DC:local ldap_passwd=xxxxxxxx ldap_search_base=OU:Vlaamseoogpunten,DC:BLL,DC:local field_user_principal=userPrincipalName ldap_auth_type=SIMPLE ldap_sync_password_to_om=no 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 ldap_use_lower_case=false I copied the working config to the new but that doesn't work anymore in the new version apparently, so the new config: ldap_conn_host=192.168.x.x ldap_conn_port=389 ldap_conn_secure=false ldap_admin_dn=CN= openmeetingsLDAPuser,CN=Users,DC=BLL,DC=local ldap_passwd=xxxxxxxxx ldap_search_base=OU=Vlaamseoogpunten,DC=BLL,DC=local ldap_search_query=(&(objectCategory=person)(objectClass=person)(sAMAccountName=%1$s)) ldap_search_scope=SUBTREE ldap_auth_type=SIMPLEBIND ldap_userdn_format=sAMAccountName=%s,OU=Vlaamseoogpunten,DC=BLL,DC=local ldap_provisionning=AUTOUPDATE ldap_deref_mode=always ldap_use_admin_to_get_attrs=true ldap_sync_password_to_om=false 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 ldap_use_lower_case=false When I try to login now, I get "Wrong password" but I don't think that has anything to do with it. In openmeetings log, I don't find anything about the user I tried to login with or maybe the loglevel is not high enough ? Can I change that ? Anybody an idea ? Thanks, Ph. <a href="http://www.blindenzorglichtenliefde.be/nl/Schenken"><img src="http://images.lichtenliefde.be/mailfooters/schenken.jpg" alt="Schenk Online" name="schenk Online" width="170" height="125" border="0" id="Schenk Online"/></a> -- WBR Maxim aka solomax <a href="http://www.blindenzorglichtenliefde.be/nl/Schenken"><img src="http://images.lichtenliefde.be/mailfooters/schenken.jpg" alt="Schenk Online" name="schenk Online" width="170" height="125" border="0" id="Schenk Online"/></a>