Hello, It's me again... I'm back. Now I have a new problem to connect to my AD... In log file it is write : *ERROR ......... Not authenticated* witch is a quite better message than before but after that it is write : *LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece\00 at........*
I try to understand my problem but "AcceptSecurityContext error" seems to speack about a security problem. I have set my ldap_conn_secure=false in om_ldap.conf. I don't understand what could be my problem. thanks a lot for your ideas. Greg. 2014-09-18 15:37 GMT+02:00 Grégory Mangeney <mange...@gmail.com>: > Ok, I finally understand that I have to put the filename and only the > filename without */usr/lib/red5/webapps/openmeetings/conf/* > > Now I have a new message whitch said me invalid password... > It's quite better... > Thank you... > I could continue to try to set it now. > bye > > Greg. > > > > 2014-09-18 15:06 GMT+02:00 Maxim Solodovnik <solomax...@gmail.com>: > >> you need to write file name relative to webapps/openmeetings/conf folder >> in your case *om_ldap.cfg *should be specified >> >> On 18 September 2014 20:04, Grégory Mangeney <mange...@gmail.com> wrote: >> >>> Thank you very much but I don't understand very well. >>> I think I put the right information... >>> Do you want to say that I have to write : >>> */usr/lib/red5/webapps/openmeetings/conf/* without the filename >>> *om_ldap.cfg* at the end? >>> Thanks for your help >>> Greg >>> >>> >>> 2014-09-18 14:52 GMT+02:00 Maxim Solodovnik <solomax...@gmail.com>: >>> >>>> AFAIK the path should be relative to /usr/lib/red5/webapps/ >>>> openmeetings/conf >>>> Please change this path >>>> >>>> Additionally you can file JIRA issue to add check to the Admin screen >>>> (so path will be validated on enter) >>>> >>>> On 18 September 2014 19:44, Grégory Mangeney <mange...@gmail.com> >>>> wrote: >>>> >>>>> Hello, >>>>> I have the same problem: I could not connect with AD. >>>>> I have the domain at the login screen, >>>>> I am using the 3.0.3. >>>>> I found this line in my log file :* ERROR 09-18 14:28:33.994 >>>>> o.a.o.l.LdapLoginManagement:147 [http-nio-0.0.0.0-5080-exec-4] - Error on >>>>> LdapLogin : Configurationdata couldnt be retrieved!* >>>>> >>>>> This seem strange because in my LDAP config (in openmeetings >>>>> Administration/LDAP menu), I put the correct path in the "Config file >>>>> name" >>>>> : /usr/lib/red5/webapps/openmeetings/conf/om_ldap.cfg >>>>> >>>>> Why is this error appeared : *Configurationdata couldnt be >>>>> retrieved! *??? >>>>> >>>>> >>>>> Thanks a lot >>>>> >>>>> Greg >>>>> >>>>> >>>>> 2014-09-17 12:52 GMT+02:00 Maxim Solodovnik <solomax...@gmail.com>: >>>>> >>>>>> great :) >>>>>> >>>>>> On 17 September 2014 17:46, Teddy Jayasaputra < >>>>>> teddy.jayasapu...@ocbcnisp.com> wrote: >>>>>> >>>>>>> Dear Maxim, >>>>>>> >>>>>>> After close look to console log. >>>>>>> We found this error : >>>>>>> ERROR 09-17 17:28:33.278 LdapLoginManagement.java 135070 285 >>>>>>> org.apache.openmeetings.ldap.LdapLoginManagement >>>>>>> [http-nio-0.0.0.0-5080-exec-6] - User not found in OM DB and >>>>>>> Provisionning.AUTOCREATE was not set >>>>>>> >>>>>>> After we change ldapconfiguration file from ldap_provisionning=NONE >>>>>>> to AUTOCREATE we can login using AD. >>>>>>> >>>>>>> thanks. >>>>>>> >>>>>>> Best Regards, >>>>>>> >>>>>>> >>>>>>> -Teddy Jayasaputra- >>>>>>> >>>>>>> >>>>>>> On 9/17/2014 4:25 PM, Maxim Solodovnik wrote: >>>>>>> >>>>>>> do you have your AD domain on the login screen? >>>>>>> are there errors in the log? >>>>>>> what OM version are you using? >>>>>>> >>>>>>> On 17 September 2014 16:02, ARI HENDIAWAN < >>>>>>> ari.hendia...@ocbcnisp.com> wrote: >>>>>>> >>>>>>>> Dear all, >>>>>>>> please we need extra information how to integrate openmeetings >>>>>>>> 3.0.3 with AD? >>>>>>>> we already setting on ldap.conf and still problem.. if we saw on AD >>>>>>>> , user that want sign-in openmeetings success, but on login menu >>>>>>>> openmeetings shown error "invalid password" >>>>>>>> >>>>>>>> >>>>>>>> Tks >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Disclaimer : >>>>>>>> Confidential information may be contained in this message. If you >>>>>>>> are not the intended recipient, you are strictly prohibited and may be >>>>>>>> unlawful to use, copy, store, distribute, disclose or communicate any >>>>>>>> part >>>>>>>> of it to others and you are obliged to return it immediately to sender >>>>>>>> or >>>>>>>> notify us and delete the e-mail and any attachments from your system. >>>>>>>> Opinions, conclusions and other information in this e-mail that do not >>>>>>>> relate to the official business of any PT Bank OCBC NISP Tbk shall be >>>>>>>> understood as neither given nor endorsed by it. No assumption of >>>>>>>> responsibility or liability whatsoever is undertaken by PT Bank OCBC >>>>>>>> NISP >>>>>>>> Tbk in respect of prohibited and unauthorised use by any other person. >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> WBR >>>>>>> Maxim aka solomax >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Disclaimer : >>>>>>> Confidential information may be contained in this message. If you >>>>>>> are not the intended recipient, you are strictly prohibited and may be >>>>>>> unlawful to use, copy, store, distribute, disclose or communicate any >>>>>>> part >>>>>>> of it to others and you are obliged to return it immediately to sender >>>>>>> or >>>>>>> notify us and delete the e-mail and any attachments from your system. >>>>>>> Opinions, conclusions and other information in this e-mail that do not >>>>>>> relate to the official business of any PT Bank OCBC NISP Tbk shall be >>>>>>> understood as neither given nor endorsed by it. No assumption of >>>>>>> responsibility or liability whatsoever is undertaken by PT Bank OCBC >>>>>>> NISP >>>>>>> Tbk in respect of prohibited and unauthorised use by any other person. >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> WBR >>>>>> Maxim aka solomax >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> WBR >>>> Maxim aka solomax >>>> >>> >>> >> >> >> -- >> WBR >> Maxim aka solomax >> > >
