Re: LDAP on OpenMeetings 0.7 RC2

2009-02-12 Thread smoeker
hi there, at login time u need to enter the UserPrinicipalName, so it depends, how its written in the Active Directory... -> in other words : there is nothing implemented within OpenMeetings to cut off domain name of the users LDAP prinicipal name... see ya Smoeker P.S.: cool, that it works

Re: LDAP on OpenMeetings 0.7 RC2

2009-02-12 Thread Slurb
hi, Thanks, it works, this morning I can not me login with LDAP, now I can connect to LDAP but for the login I need to use the domain : In my om_ldap.cfg I have : ldap_login_base=OU:Utilisateurs,OU:VILLEROY,DC:listel,DC:local ldap_search_base=DC:listel,DC:local In the login OM page, I am comp

Re: LDAP on OpenMeetings 0.7 RC2

2009-02-11 Thread smoeker
hi, ldap_config_path is a config value , stored in the configuration table of OpenMeetings database(the configuration vals are written during installation process...) -> you can modify/add configuration values using the administraion panel within OM -> just add the configuration key "ldap_config

Re: LDAP on OpenMeetings 0.7 RC2

2009-02-11 Thread Slurb
Thank you for your quick response, but I don't understand where "ldap_config_path" is used (because by default it is commented out in om_ldap.cfg) ?? I filled the fields for : "ldap_conn_url", "ldap_admin", "ldap_passwd", "ldap_login_base" and "ldap_search_base" in om_ldap.cfg but it is "ldap

Re: LDAP on OpenMeetings 0.7 RC2

2009-02-11 Thread smoeker
hi, you dont need changes in your hibernate config - the LDAP auth controls the entered data agaisnt the Ldap server, configured in om_ldap.cfg, in case of success, the userdata gets written within the normal OM database... -> the Ldap auth only is active, when u configured the key ldap_config_p

LDAP on OpenMeetings 0.7 RC2

2009-02-11 Thread Slurb
Hi, I installed openmeetings 0.7 RC2, but I do not know how to use ldap, I configured the file om_ldap.cfg, but I do not know whether to make changes in hibernate.cfg.xml ... Sorry for my English Slurb --~--~-~--~~~---~--~~ You received this message because