Hi All: I have the latest release of OM running in a DEBIAN machine, I am authenticating the users using a Windows 2003 Server with AD. I was having problem authenticating the users and I put an sniffer to check what happen. As per the sniffer capture seems that the OM is trying to do a bind to the LDAP server to authenticate the user instead of retrieve the user info. I tested with a LDAP navigator and with the Windows Admin user account I am able to bind to the LDAP server but not with the regular user. In the same way I am able to loging to the OM using the Windows Admin account but no with the regular user as the bind fail. Can you tell me if I am doing something wrong?
Here is the ldap.cfg #ConfigurationFile for LDAP Auth #specify the LDAP Server type ldap_server_type=AD #LDAP URL ldap_conn_url=ldap://172.16.118.110:389 #Login distinguished name (DN) for Authentification on LDAP Server - keep emtpy if not requiered ldap_admin_dn=CN:admin,OU:Services_Accounts,OU:Compay,DC:ad,DC:company,DC:com #Loginpass for Authentification on LDAP Server - keep emtpy if not requiered ldap_passwd=************* #base to search for userdata(of user, that wants to login ldap_search_base=OU:Users,OU:Compay,DC:ad,DC:company,DC:com # Fieldnames (can differ between Ldap servers) field_user_principal=sAMAccountName # Ldap auth type(SIMPLE,NONE) ldap_auth_type=SIMPLE # Ldap-password synchronization to OM DB # Set this to 'yes' if you want OM to synchronize the user Ldap- password to OM$ # This enables local login of users if the ldap server is offline. # If you want to disable the feature, set this to 'no'. # Defautl value is 'yes' ldap_sync_password_to_om=no Regards and Thanks Jorge -- You received this message because you are subscribed to the Google Groups "OpenMeetings User" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/openmeetings-user?hl=en.
