You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Mahmut TEKER <te...@gmail.com> on 2012/02/07 14:07:55 UTC
2 important issue (LDAP default domain and Moodle plug-in)
Hi,
In our system we faced with two important problems, we also want to
ask you;
1) We have enabled LDAP login in our system (with no problem), but we
want to make the LDAP domain as the default domain on the login page.
How can we do it? We tried to change the "checkLoginData.lzx" according
to this link
http://groups.google.com/group/openmeetings-dev/browse_thread/thread/21d719ae2f07c0ef
but we could not achieve. Also we want to remove color-style and quality
parts but the default domain is more important for us.
2) We also installed Moodle plug-in into our Moodle site and achieved
connection between both of them. However, the scenario we have faced
that, ( our Moodle site and OM site use the same LDAP tree) when a user
logs into Moodle site and then makes a connection to OM, system is
creating a user according to the username in Moodle. After the
videoconference made from Moodle, the created user remains in the system
as Disabled. And then when the same user tries to connect OM from OM
site, system does not allow him/her to login because there is already a
username with the same name but which is disabled.
As a result, users connecting from Moodle can not login OM directly
because there remains a same username. Moreover, as the admin I can not
make any change on the user (except for deleting him/her from users
table) such as on the organisation etc...
I hope you can help me,
Best Regards,
_Mahmut
Re: 2 important issue (LDAP default domain and Moodle plug-in)
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
There is need for a mininal change in the source code and you need to
compile a binary.
The neccessary source code change is:
You change in LdapLoginmanagement.java ~400
replace "getUserByLogin"
with "getUserByLoginOrEmail"
This will have the desired effect.
then you need to compile a binary using ANT.
You might better use a very early revision from SVN (or even the revision
from the old repository that is the same as the Release that you would like
to fix)
Sebastian
2012/2/10 Mahmut TEKER <te...@gmail.com>
> Hi Sebastian,
>
> So in our case I think there is no solution am I wrong?
>
> We use one LDAP server and use it on both Moodle and OM.
>
> In my case it can work for me that if the OM plugin on Moodle does not
> create the same user on OM. If it is possible how can I implement this? No
> problem for us to make different drives. I can tell my user staff that the
> person logged from Moodle is different from the ones OM itself because it
> even better for us.
>
> In this situation my Moodle users can not login to the OM site and
> which is critical for us.
>
> Any help is appreciated. Thank you very much.
>
> Regards,
>
>
> _Mahmut
>
> On 02/07/2012 04:42 PM, seba.wagner@gmail.com wrote:
>
> *"Module Key". What should it be?*
> => any random string, it is for integrating multiple Moodle (or whatever)
> systems with a single instance of OpenMeetings. The module key is called
> internally "type" and must be unique per Moodle instance.
> The moduleKey/type-param is used in the setUser method to create the user
> record and when simulating the external user in OpenMeetings. The final
> result is that the combination of externalUserId + moduleKey/type-param
> must be unique in the openmeetings database.
>
> But you're right, the check method in the LDAP login procedure is wrong,
> it does only check on the username, not on the additional params
> externalUserId + type.
> We will need to extend this check in the ldpa login, if the user has an
> externalUserId/type then add a new user or just ignore those.
> The disadvantage of that will be that LDAP users and Moodle users are
> separated, so you have two user records for the same user and every user
> will have its own private drive in the File-Explorer of the conference room.
>
> Sebastian
>
> 2012/2/7 Mahmut TEKER <te...@gmail.com>
>
>> Hi,
>>
>> I have found it yes there is a place called "Module Key". What should
>> it be?, it is "Moodle" right now. Is there any documentation you can
>> provide?
>>
>> Thank you very much,
>>
>> Best Regards,
>>
>>
>> _Mahmut
>>
>> 07.02.2012 15:37, seba.wagner@gmail.com yazmış:
>>
>> There is one, it is called "Module Key" and its the second param from the
>> bottom in the module configuration
>>
>> Sebastian
>>
>> 2012/2/7 Mahmut TEKER <te...@gmail.com>
>>
>>> Hi Sebastian,
>>>
>>> If I am not wrong, there is no API_KEY place in the Moodle plug-in
>>> site. Can you explain it more.
>>>
>>> Thank you very much,
>>>
>>> Regards,
>>>
>>>
>>> _Mahmut
>>>
>>> 07.02.2012 15 <07.02.2012%2015>:25, seba.wagner@gmail.com yazmış:
>>>
>>> Have you configured the API_KEY in the moodle plugin configuration ?
>>>
>>> Sebastian
>>>
>>> 2012/2/7 Mahmut TEKER <te...@gmail.com>
>>>
>>>> Hi,
>>>>
>>>> In our system we faced with two important problems, we also want to
>>>> ask you;
>>>>
>>>> 1) We have enabled LDAP login in our system (with no problem), but we
>>>> want to make the LDAP domain as the default domain on the login page. How
>>>> can we do it? We tried to change the "checkLoginData.lzx" according to this
>>>> link
>>>> http://groups.google.com/group/openmeetings-dev/browse_thread/thread/21d719ae2f07c0efbut we could not achieve. Also we want to remove color-style and quality
>>>> parts but the default domain is more important for us.
>>>>
>>>> 2) We also installed Moodle plug-in into our Moodle site and achieved
>>>> connection between both of them. However, the scenario we have faced that,
>>>> ( our Moodle site and OM site use the same LDAP tree) when a user logs into
>>>> Moodle site and then makes a connection to OM, system is creating a user
>>>> according to the username in Moodle. After the videoconference made from
>>>> Moodle, the created user remains in the system as Disabled. And then when
>>>> the same user tries to connect OM from OM site, system does not allow
>>>> him/her to login because there is already a username with the same name but
>>>> which is disabled.
>>>>
>>>>
>>>> As a result, users connecting from Moodle can not login OM directly
>>>> because there remains a same username. Moreover, as the admin I can not
>>>> make any change on the user (except for deleting him/her from users table)
>>>> such as on the organisation etc...
>>>>
>>>>
>>>> I hope you can help me,
>>>>
>>>>
>>>> Best Regards,
>>>>
>>>>
>>>> _Mahmut
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Sebastian Wagner
>>> http://www.openmeetings.de
>>> http://incubator.apache.org/openmeetings/
>>> http://www.webbase-design.de
>>> http://www.wagner-sebastian.com
>>> seba.wagner@gmail.com
>>>
>>>
>>>
>>
>>
>> --
>> Sebastian Wagner
>> http://www.openmeetings.de
>> http://incubator.apache.org/openmeetings/
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> seba.wagner@gmail.com
>>
>>
>>
>
>
> --
> Sebastian Wagner
> http://www.openmeetings.de
> http://incubator.apache.org/openmeetings/
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>
>
>
--
Sebastian Wagner
http://www.openmeetings.de
http://incubator.apache.org/openmeetings/
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: 2 important issue (LDAP default domain and Moodle plug-in)
Posted by Mahmut TEKER <te...@gmail.com>.
Hi Sebastian,
So in our case I think there is no solution am I wrong?
We use one LDAP server and use it on both Moodle and OM.
In my case it can work for me that if the OM plugin on Moodle does
not create the same user on OM. If it is possible how can I implement
this? No problem for us to make different drives. I can tell my user
staff that the person logged from Moodle is different from the ones OM
itself because it even better for us.
In this situation my Moodle users can not login to the OM site and
which is critical for us.
Any help is appreciated. Thank you very much.
Regards,
_Mahmut
On 02/07/2012 04:42 PM, seba.wagner@gmail.com wrote:
> *"Module Key". What should it be?*
> => any random string, it is for integrating multiple Moodle (or
> whatever) systems with a single instance of OpenMeetings. The module
> key is called internally "type" and must be unique per Moodle instance.
> The moduleKey/type-param is used in the setUser method to create the
> user record and when simulating the external user in OpenMeetings. The
> final result is that the combination of externalUserId +
> moduleKey/type-param must be unique in the openmeetings database.
>
> But you're right, the check method in the LDAP login procedure is
> wrong, it does only check on the username, not on the additional
> params externalUserId + type.
> We will need to extend this check in the ldpa login, if the user has
> an externalUserId/type then add a new user or just ignore those.
> The disadvantage of that will be that LDAP users and Moodle users are
> separated, so you have two user records for the same user and every
> user will have its own private drive in the File-Explorer of the
> conference room.
>
> Sebastian
>
> 2012/2/7 Mahmut TEKER <teker.mahmut@gmail.com
> <ma...@gmail.com>>
>
> Hi,
>
> I have found it yes there is a place called "Module Key". What
> should it be?, it is "Moodle" right now. Is there any
> documentation you can provide?
>
> Thank you very much,
>
> Best Regards,
>
>
> _Mahmut
>
> 07.02.2012 15 <tel:07.02.2012%2015>:37, seba.wagner@gmail.com
> <ma...@gmail.com> yazmış:
>> There is one, it is called "Module Key" and its the second param
>> from the bottom in the module configuration
>>
>> Sebastian
>>
>> 2012/2/7 Mahmut TEKER <teker.mahmut@gmail.com
>> <ma...@gmail.com>>
>>
>> Hi Sebastian,
>>
>> If I am not wrong, there is no API_KEY place in the Moodle
>> plug-in site. Can you explain it more.
>>
>> Thank you very much,
>>
>> Regards,
>>
>>
>> _Mahmut
>>
>> 07.02.2012 15 <tel:07.02.2012%2015>:25, seba.wagner@gmail.com
>> <ma...@gmail.com> yazmış:
>>> Have you configured the API_KEY in the moodle plugin
>>> configuration ?
>>>
>>> Sebastian
>>>
>>> 2012/2/7 Mahmut TEKER <teker.mahmut@gmail.com
>>> <ma...@gmail.com>>
>>>
>>> Hi,
>>>
>>> In our system we faced with two important problems, we
>>> also want to ask you;
>>>
>>> 1) We have enabled LDAP login in our system (with no
>>> problem), but we want to make the LDAP domain as the
>>> default domain on the login page. How can we do it? We
>>> tried to change the "checkLoginData.lzx" according to
>>> this link
>>> http://groups.google.com/group/openmeetings-dev/browse_thread/thread/21d719ae2f07c0ef
>>> but we could not achieve. Also we want to remove
>>> color-style and quality parts but the default domain is
>>> more important for us.
>>>
>>> 2) We also installed Moodle plug-in into our Moodle site
>>> and achieved connection between both of them. However,
>>> the scenario we have faced that, ( our Moodle site and
>>> OM site use the same LDAP tree) when a user logs into
>>> Moodle site and then makes a connection to OM, system is
>>> creating a user according to the username in Moodle.
>>> After the videoconference made from Moodle, the created
>>> user remains in the system as Disabled. And then when
>>> the same user tries to connect OM from OM site, system
>>> does not allow him/her to login because there is already
>>> a username with the same name but which is disabled.
>>>
>>>
>>> As a result, users connecting from Moodle can not login
>>> OM directly because there remains a same username.
>>> Moreover, as the admin I can not make any change on the
>>> user (except for deleting him/her from users table) such
>>> as on the organisation etc...
>>>
>>>
>>> I hope you can help me,
>>>
>>>
>>> Best Regards,
>>>
>>>
>>> _Mahmut
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sebastian Wagner
>>> http://www.openmeetings.de
>>> http://incubator.apache.org/openmeetings/
>>> http://www.webbase-design.de
>>> http://www.wagner-sebastian.com
>>> seba.wagner@gmail.com <ma...@gmail.com>
>>
>>
>>
>>
>> --
>> Sebastian Wagner
>> http://www.openmeetings.de
>> http://incubator.apache.org/openmeetings/
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> seba.wagner@gmail.com <ma...@gmail.com>
>
>
>
>
> --
> Sebastian Wagner
> http://www.openmeetings.de
> http://incubator.apache.org/openmeetings/
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com <ma...@gmail.com>
Re: 2 important issue (LDAP default domain and Moodle plug-in)
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
*"Module Key". What should it be?*
=> any random string, it is for integrating multiple Moodle (or whatever)
systems with a single instance of OpenMeetings. The module key is called
internally "type" and must be unique per Moodle instance.
The moduleKey/type-param is used in the setUser method to create the user
record and when simulating the external user in OpenMeetings. The final
result is that the combination of externalUserId + moduleKey/type-param
must be unique in the openmeetings database.
But you're right, the check method in the LDAP login procedure is wrong, it
does only check on the username, not on the additional params
externalUserId + type.
We will need to extend this check in the ldpa login, if the user has an
externalUserId/type then add a new user or just ignore those.
The disadvantage of that will be that LDAP users and Moodle users are
separated, so you have two user records for the same user and every user
will have its own private drive in the File-Explorer of the conference room.
Sebastian
2012/2/7 Mahmut TEKER <te...@gmail.com>
> Hi,
>
> I have found it yes there is a place called "Module Key". What should
> it be?, it is "Moodle" right now. Is there any documentation you can
> provide?
>
> Thank you very much,
>
> Best Regards,
>
>
> _Mahmut
>
> 07.02.2012 15:37, seba.wagner@gmail.com yazmış:
>
> There is one, it is called "Module Key" and its the second param from the
> bottom in the module configuration
>
> Sebastian
>
> 2012/2/7 Mahmut TEKER <te...@gmail.com>
>
>> Hi Sebastian,
>>
>> If I am not wrong, there is no API_KEY place in the Moodle plug-in
>> site. Can you explain it more.
>>
>> Thank you very much,
>>
>> Regards,
>>
>>
>> _Mahmut
>>
>> 07.02.2012 15:25, seba.wagner@gmail.com yazmış:
>>
>> Have you configured the API_KEY in the moodle plugin configuration ?
>>
>> Sebastian
>>
>> 2012/2/7 Mahmut TEKER <te...@gmail.com>
>>
>>> Hi,
>>>
>>> In our system we faced with two important problems, we also want to
>>> ask you;
>>>
>>> 1) We have enabled LDAP login in our system (with no problem), but we
>>> want to make the LDAP domain as the default domain on the login page. How
>>> can we do it? We tried to change the "checkLoginData.lzx" according to this
>>> link
>>> http://groups.google.com/group/openmeetings-dev/browse_thread/thread/21d719ae2f07c0efbut we could not achieve. Also we want to remove color-style and quality
>>> parts but the default domain is more important for us.
>>>
>>> 2) We also installed Moodle plug-in into our Moodle site and achieved
>>> connection between both of them. However, the scenario we have faced that,
>>> ( our Moodle site and OM site use the same LDAP tree) when a user logs into
>>> Moodle site and then makes a connection to OM, system is creating a user
>>> according to the username in Moodle. After the videoconference made from
>>> Moodle, the created user remains in the system as Disabled. And then when
>>> the same user tries to connect OM from OM site, system does not allow
>>> him/her to login because there is already a username with the same name but
>>> which is disabled.
>>>
>>>
>>> As a result, users connecting from Moodle can not login OM directly
>>> because there remains a same username. Moreover, as the admin I can not
>>> make any change on the user (except for deleting him/her from users table)
>>> such as on the organisation etc...
>>>
>>>
>>> I hope you can help me,
>>>
>>>
>>> Best Regards,
>>>
>>>
>>> _Mahmut
>>>
>>>
>>>
>>
>>
>> --
>> Sebastian Wagner
>> http://www.openmeetings.de
>> http://incubator.apache.org/openmeetings/
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> seba.wagner@gmail.com
>>
>>
>>
>
>
> --
> Sebastian Wagner
> http://www.openmeetings.de
> http://incubator.apache.org/openmeetings/
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>
>
>
--
Sebastian Wagner
http://www.openmeetings.de
http://incubator.apache.org/openmeetings/
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: 2 important issue (LDAP default domain and Moodle plug-in)
Posted by Mahmut TEKER <te...@gmail.com>.
Hi,
I have found it yes there is a place called "Module Key". What
should it be?, it is "Moodle" right now. Is there any documentation you
can provide?
Thank you very much,
Best Regards,
_Mahmut
07.02.2012 15:37, seba.wagner@gmail.com yazmış:
> There is one, it is called "Module Key" and its the second param from
> the bottom in the module configuration
>
> Sebastian
>
> 2012/2/7 Mahmut TEKER <teker.mahmut@gmail.com
> <ma...@gmail.com>>
>
> Hi Sebastian,
>
> If I am not wrong, there is no API_KEY place in the Moodle
> plug-in site. Can you explain it more.
>
> Thank you very much,
>
> Regards,
>
>
> _Mahmut
>
> 07.02.2012 15 <tel:07.02.2012%2015>:25, seba.wagner@gmail.com
> <ma...@gmail.com> yazmış:
>> Have you configured the API_KEY in the moodle plugin configuration ?
>>
>> Sebastian
>>
>> 2012/2/7 Mahmut TEKER <teker.mahmut@gmail.com
>> <ma...@gmail.com>>
>>
>> Hi,
>>
>> In our system we faced with two important problems, we also
>> want to ask you;
>>
>> 1) We have enabled LDAP login in our system (with no
>> problem), but we want to make the LDAP domain as the default
>> domain on the login page. How can we do it? We tried to
>> change the "checkLoginData.lzx" according to this link
>> http://groups.google.com/group/openmeetings-dev/browse_thread/thread/21d719ae2f07c0ef
>> but we could not achieve. Also we want to remove color-style
>> and quality parts but the default domain is more important
>> for us.
>>
>> 2) We also installed Moodle plug-in into our Moodle site and
>> achieved connection between both of them. However, the
>> scenario we have faced that, ( our Moodle site and OM site
>> use the same LDAP tree) when a user logs into Moodle site and
>> then makes a connection to OM, system is creating a user
>> according to the username in Moodle. After the
>> videoconference made from Moodle, the created user remains in
>> the system as Disabled. And then when the same user tries to
>> connect OM from OM site, system does not allow him/her to
>> login because there is already a username with the same name
>> but which is disabled.
>>
>>
>> As a result, users connecting from Moodle can not login OM
>> directly because there remains a same username. Moreover, as
>> the admin I can not make any change on the user (except for
>> deleting him/her from users table) such as on the
>> organisation etc...
>>
>>
>> I hope you can help me,
>>
>>
>> Best Regards,
>>
>>
>> _Mahmut
>>
>>
>>
>>
>>
>> --
>> Sebastian Wagner
>> http://www.openmeetings.de
>> http://incubator.apache.org/openmeetings/
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> seba.wagner@gmail.com <ma...@gmail.com>
>
>
>
>
> --
> Sebastian Wagner
> http://www.openmeetings.de
> http://incubator.apache.org/openmeetings/
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com <ma...@gmail.com>
Re: 2 important issue (LDAP default domain and Moodle plug-in)
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
There is one, it is called "Module Key" and its the second param from the
bottom in the module configuration
Sebastian
2012/2/7 Mahmut TEKER <te...@gmail.com>
> Hi Sebastian,
>
> If I am not wrong, there is no API_KEY place in the Moodle plug-in
> site. Can you explain it more.
>
> Thank you very much,
>
> Regards,
>
>
> _Mahmut
>
> 07.02.2012 15:25, seba.wagner@gmail.com yazmış:
>
> Have you configured the API_KEY in the moodle plugin configuration ?
>
> Sebastian
>
> 2012/2/7 Mahmut TEKER <te...@gmail.com>
>
>> Hi,
>>
>> In our system we faced with two important problems, we also want to ask
>> you;
>>
>> 1) We have enabled LDAP login in our system (with no problem), but we
>> want to make the LDAP domain as the default domain on the login page. How
>> can we do it? We tried to change the "checkLoginData.lzx" according to this
>> link
>> http://groups.google.com/group/openmeetings-dev/browse_thread/thread/21d719ae2f07c0efbut we could not achieve. Also we want to remove color-style and quality
>> parts but the default domain is more important for us.
>>
>> 2) We also installed Moodle plug-in into our Moodle site and achieved
>> connection between both of them. However, the scenario we have faced that,
>> ( our Moodle site and OM site use the same LDAP tree) when a user logs into
>> Moodle site and then makes a connection to OM, system is creating a user
>> according to the username in Moodle. After the videoconference made from
>> Moodle, the created user remains in the system as Disabled. And then when
>> the same user tries to connect OM from OM site, system does not allow
>> him/her to login because there is already a username with the same name but
>> which is disabled.
>>
>>
>> As a result, users connecting from Moodle can not login OM directly
>> because there remains a same username. Moreover, as the admin I can not
>> make any change on the user (except for deleting him/her from users table)
>> such as on the organisation etc...
>>
>>
>> I hope you can help me,
>>
>>
>> Best Regards,
>>
>>
>> _Mahmut
>>
>>
>>
>
>
> --
> Sebastian Wagner
> http://www.openmeetings.de
> http://incubator.apache.org/openmeetings/
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>
>
>
--
Sebastian Wagner
http://www.openmeetings.de
http://incubator.apache.org/openmeetings/
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: 2 important issue (LDAP default domain and Moodle plug-in)
Posted by Mahmut TEKER <te...@gmail.com>.
Hi Sebastian,
If I am not wrong, there is no API_KEY place in the Moodle plug-in
site. Can you explain it more.
Thank you very much,
Regards,
_Mahmut
07.02.2012 15:25, seba.wagner@gmail.com yazm?s,:
> Have you configured the API_KEY in the moodle plugin configuration ?
>
> Sebastian
>
> 2012/2/7 Mahmut TEKER <teker.mahmut@gmail.com
> <ma...@gmail.com>>
>
> Hi,
>
> In our system we faced with two important problems, we also want
> to ask you;
>
> 1) We have enabled LDAP login in our system (with no problem),
> but we want to make the LDAP domain as the default domain on the
> login page. How can we do it? We tried to change the
> "checkLoginData.lzx" according to this link
> http://groups.google.com/group/openmeetings-dev/browse_thread/thread/21d719ae2f07c0ef
> but we could not achieve. Also we want to remove color-style and
> quality parts but the default domain is more important for us.
>
> 2) We also installed Moodle plug-in into our Moodle site and
> achieved connection between both of them. However, the scenario we
> have faced that, ( our Moodle site and OM site use the same LDAP
> tree) when a user logs into Moodle site and then makes a
> connection to OM, system is creating a user according to the
> username in Moodle. After the videoconference made from Moodle,
> the created user remains in the system as Disabled. And then when
> the same user tries to connect OM from OM site, system does not
> allow him/her to login because there is already a username with
> the same name but which is disabled.
>
>
> As a result, users connecting from Moodle can not login OM
> directly because there remains a same username. Moreover, as the
> admin I can not make any change on the user (except for deleting
> him/her from users table) such as on the organisation etc...
>
>
> I hope you can help me,
>
>
> Best Regards,
>
>
> _Mahmut
>
>
>
>
>
> --
> Sebastian Wagner
> http://www.openmeetings.de
> http://incubator.apache.org/openmeetings/
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com <ma...@gmail.com>
Re: 2 important issue (LDAP default domain and Moodle plug-in)
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
Have you configured the API_KEY in the moodle plugin configuration ?
Sebastian
2012/2/7 Mahmut TEKER <te...@gmail.com>
> Hi,
>
> In our system we faced with two important problems, we also want to ask
> you;
>
> 1) We have enabled LDAP login in our system (with no problem), but we
> want to make the LDAP domain as the default domain on the login page. How
> can we do it? We tried to change the "checkLoginData.lzx" according to this
> link
> http://groups.google.com/group/openmeetings-dev/browse_thread/thread/21d719ae2f07c0efbut we could not achieve. Also we want to remove color-style and quality
> parts but the default domain is more important for us.
>
> 2) We also installed Moodle plug-in into our Moodle site and achieved
> connection between both of them. However, the scenario we have faced that,
> ( our Moodle site and OM site use the same LDAP tree) when a user logs into
> Moodle site and then makes a connection to OM, system is creating a user
> according to the username in Moodle. After the videoconference made from
> Moodle, the created user remains in the system as Disabled. And then when
> the same user tries to connect OM from OM site, system does not allow
> him/her to login because there is already a username with the same name but
> which is disabled.
>
>
> As a result, users connecting from Moodle can not login OM directly
> because there remains a same username. Moreover, as the admin I can not
> make any change on the user (except for deleting him/her from users table)
> such as on the organisation etc...
>
>
> I hope you can help me,
>
>
> Best Regards,
>
>
> _Mahmut
>
>
>
--
Sebastian Wagner
http://www.openmeetings.de
http://incubator.apache.org/openmeetings/
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com