s it has
to stream the data to each attendee. This is the biggest
bottleneck in the whole process and not the system or even
the hardware.
*Von:*Jon Cyr [mailto:j...@cloudyit.com
<mailto:j...@cloudyit.com>]
*Gesendet:* Dienstag, 14. Februar 2012 22:58
ical perspective it doesn’t prevent you from having 100 or more
>> attendees.
>>
>> The challenge with such amounts of attendees is not the system and even
>> not really the hardware –though a dedicated server with at least 8G is
>> preferred- but the bandwidth you have
en the hardware.
*Von:*Jon Cyr [mailto:j...@cloudyit.com <mailto:j...@cloudyit.com>]
*Gesendet:* Dienstag, 14. Februar 2012 22:58
*An:* openmeetings-user@incubator.apache.org
<mailto:openmeetings-user@incubator.apache.org>
*Betreff:* Re: AW: What's t
t;
> ** **
>
> *Von:* Jon Cyr [mailto:j...@cloudyit.com]
> *Gesendet:* Dienstag, 14. Februar 2012 22:58
> *An:* openmeetings-user@incubator.apache.org
> *Betreff:* Re: AW: What's the largest meeting you've run
>
> ** **
>
> Hi Norbert,
>
> It means... in non-tech
Hi Norbert,
It means... in non-technical terms, who's holding meetings, how many
people...
Real examples.
For instance... My name is Fred, I hold weekly web-seminars or webinars
with over 100 people, it works great.
Who is using this? Share an anonymous story of how it's going. Don't
wo
Yes, i have used this svn url
But i was using :
ldap_use_lower_case=yes not TRUE !!! :-( Sorry about that)
below is my current ldap.cfg file :
ldap_server_type=OpenLDAP
ldap_conn_url=ldap://xxx.xxx.x.xx:389
ldap_admin_dn=CN:x,OU:x,O:xxx
ldap_passwd=xxx
ldap_search_b
I did network packet capture. With the new code the ldap Bind Request
sended by OM is :
DN=tOTOa
So of course the ldap server answer invalidSyntax ... A correct Bind
Request will be :
DN=CN=tOTOa,OU=xx,O=xxx
morever it sends " DN=tOTOa ", but it should be in lowercase (totoa)
after your modif
Yes,
okay but I don#t know how this option should fix that, actually all it does
is to make the string "TotoA" (or whatever string) to lowercase and send it
to the LDAP server.
I cannot instruct the LDAP server to ignore lower/upper case.
So this option will be no solution to your problem.
Sebast
Sorry,
My username in ldap directory is TotoA and i've used tOTOa in the OM
login screen.
See below the logs :
___
WARN 01-26 14:36:24.997 MainService.java 7904119 338
org.openmeetings.app.remote.MainService [NioProcessor-6] - loginUser:
59
Hi benoit,
what error message do you see? Cause the one you've posted has nothing to
do with "Invalid DN Syntax".
Sebastian
2012/1/26 Benoit Vautrin
> Hi,
>
> I've ran SVN and ant yesterday evening, re-install Openmeeting from
> scratch, but i've still exactly the same behaviours.
>
> When i t
Hi,
I've ran SVN and ant yesterday evening, re-install Openmeeting from
scratch, but i've still exactly the same behaviours.
When i try to login without enforce lower/upper case as it is in my
ldap directory I see an Invalid DN Syntax error message in logs.
Regards.
Benoit
>>> "seba.wag...@
*by downloading the nightly build*
=> Sorry but the Nightly Builds are currently pointing to the wrong SVN
(and Apache Infrastructure is not set up yet)
You will have to download the code from the SVN by yourself and compile it
using ANT.
Sebastian
2012/1/25 Benoit Vautrin
> Hi,
>
> I've tested
Hi,
I've tested your new code (by downloading the nightly build). I have
added the option in my ldap config file :
ldap_use_lower_case=yes
When i try to login without enforce lower/upper case as it is in my
ldap directory see below the error :
---
Hi,
I've not be able to use SVN yet. I plan to wait the nighly build and
test tomorrow morning ...
I would like to explain me much better :-(
in my example:
in my ldap server, username = TotoA
if i use " TotoA " in the OM login window, the bind request is correct
" DN=CN=TotoA,ou=users,o=corp "
Hi Benoit,
sorry I don't get it now. What version of OpenMeetings are you testing?
*when i did a request without respecting uppercase/lowercase*
=> Why should TotoA by automatically lowercased' ?! Did you checkout
OpenMeetings SVN version from the Apache Repository testing the new feature
that I
Hi Sebastian,
So maybe the problem is somewhere else ... I did some packet network
capture :
when i did a request with the exact username (respecting
uppercase/lowercase) the bind request is " DN=CN=TotoA,ou=users,o=corp "
(so it works and i can login)
when i did a request without respecting uppe
So to sum up:
All the option does is to convert the username to lowercase, expecting your
ldap server to either ignore the upper/lowercase or actually having the
names really in lowercase in ldap.
Sebastian
2012/1/24 seba.wag...@gmail.com
> No I don't convert anything like that, there is no suc
No I don't convert anything like that, there is no such possibility I don't
get any user from LDAP.
All I do is search the LDAP Server for a user, if the ldap_use_lower_case
is true, the user that searchs the LDAP server is transformed to lowercase.
OpenMeetings itself will also use the lowercase u
Hi Sebastian,
I'm not a good developer but i try to understand your new code. If the
new param ldap_use_lower_case is added to the config file, you convert
in lower case the value fill-in by users in the Openmeetings login
window ? am i right ?
But i don't see where you convert also in lower case
I've resolved the issue:
there is a new param ldap_use_lower_case that you can add in the config
file.
If the param is true, the username is converted to lowercase before
validating the username.
This has no effect on how the password is verified.
https://issues.apache.org/jira/browse/OPENMEETING
LDAP usernames, as I understand it, should be case insensitive.
On Jan 23, 2012 3:19 PM, "Norbert Haag" wrote:
> Quite frankly I think that this behavior is an not an issue but a feature.
> Unix system have a strict distinction between caps and non-caps for a good
> reason. So please don't chan
Ok, I found the post recorder log messages and it seems that it can't find
the raw recording files in the streams directory, which would explain why it
has issues processing them, no? :-)
=> No that could simply mean that one of the conversion jobs fails, so
that the next stop does not find the fil
Hi,
Could it be folder writing permission problem? Have you checked the
web user's permission to write into streams folder?
Have a nice day,
_Mahmut
On 01/18/2012 03:57 PM, Norbert Haag wrote:
Ok, I found the post recorder log messages and it seems that it can't find
the raw recordin
23 matches
Mail list logo
