You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by "LeBlanc, Brad A" <bl...@tulane.edu> on 2014/06/11 15:52:14 UTC
Auto-Enrollment
We are currently using AD for our authentication for Openmeetings. All of
our users are in the same OU in our Active Directory. When any new user,
who's a member of the Accounts OU, logs in for the first time, their account
is autocreated as a web user and grants them access to the public rooms and
their own private rooms. We don't want all members of the University to
have access to this application. Is there a way to limit who is authorized
to access the application while using AD without segmenting the OU?
B. LeBlanc
Re: Auto-Enrollment
Posted by Maxim Solodovnik <so...@gmail.com>.
I'm going to re-write LDAP code (OPENMEETINGS-964
<https://issues.apache.org/jira/browse/OPENMEETINGS-964>) you can propose
attribute and help with testing
On 12 June 2014 21:06, LeBlanc, Brad A <bl...@tulane.edu> wrote:
> I looked through the sample config files and I can’t find anything
> allowing a special attribute or custom ldap query. Do you have any example
> configs? An ideal option would be to limit it to a Security Group
> membership, but looking through the forums / docs, I can’t find the
> appropriate variable to set that would customize the query sent to the
> directory.
>
>
>
> Thanks,
>
> Brad A LeBlanc
>
>
>
> *From:* Maxim Solodovnik [mailto:solomax666@gmail.com]
> *Sent:* Thursday, June 12, 2014 2:16 AM
> *To:* Openmeetings user-list
> *Subject:* Re: Auto-Enrollment
>
>
>
> Maybe some additional search criteria can be used? like special attribute?
>
>
>
> On 11 June 2014 21:22, Alexei Fedotov <al...@gmail.com> wrote:
>
> Hi Brad,
>
>
>
> some segmentation already exists because only "some" users are allowed to
> use the app. If you don't want to segment the LDAP directory, you should
> segment some other information storage, e.g. remove LDAP authentication and
> use OM database for those who are allowed to participate.
>
>
>
>
>
>
> --
> With best regards / с наилучшими пожеланиями,
> Alexei Fedotov / Алексей Федотов,
> http://dataved.ru/
> +7 916 562 8095
>
> [1] Start using Apache Openmeetings today, http://openmeetings.apache.org/
> [2] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
> [3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
>
>
>
> On Wed, Jun 11, 2014 at 5:52 PM, LeBlanc, Brad A <bl...@tulane.edu>
> wrote:
>
> We are currently using AD for our authentication for Openmeetings. All of
> our users are in the same OU in our Active Directory. When any new user,
> who’s a member of the Accounts OU, logs in for the first time, their
> account is autocreated as a web user and grants them access to the public
> rooms and their own private rooms. We don’t want all members of the
> University to have access to this application. Is there a way to limit who
> is authorized to access the application while using AD without segmenting
> the OU?
>
>
>
> B. LeBlanc
>
>
>
>
>
>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
RE: Auto-Enrollment
Posted by "LeBlanc, Brad A" <bl...@tulane.edu>.
I looked through the sample config files and I can’t find anything allowing a special attribute or custom ldap query. Do you have any example configs? An ideal option would be to limit it to a Security Group membership, but looking through the forums / docs, I can’t find the appropriate variable to set that would customize the query sent to the directory.
Thanks,
Brad A LeBlanc
From: Maxim Solodovnik [mailto:solomax666@gmail.com]
Sent: Thursday, June 12, 2014 2:16 AM
To: Openmeetings user-list
Subject: Re: Auto-Enrollment
Maybe some additional search criteria can be used? like special attribute?
On 11 June 2014 21:22, Alexei Fedotov <alexei.fedotov@gmail.com <ma...@gmail.com> > wrote:
Hi Brad,
some segmentation already exists because only "some" users are allowed to use the app. If you don't want to segment the LDAP directory, you should segment some other information storage, e.g. remove LDAP authentication and use OM database for those who are allowed to participate.
--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://dataved.ru/
+7 916 562 8095
[1] Start using Apache Openmeetings today, http://openmeetings.apache.org/
[2] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
[3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
On Wed, Jun 11, 2014 at 5:52 PM, LeBlanc, Brad A <bleblanc@tulane.edu <ma...@tulane.edu> > wrote:
We are currently using AD for our authentication for Openmeetings. All of our users are in the same OU in our Active Directory. When any new user, who’s a member of the Accounts OU, logs in for the first time, their account is autocreated as a web user and grants them access to the public rooms and their own private rooms. We don’t want all members of the University to have access to this application. Is there a way to limit who is authorized to access the application while using AD without segmenting the OU?
B. LeBlanc
--
WBR
Maxim aka solomax
Re: Auto-Enrollment
Posted by Maxim Solodovnik <so...@gmail.com>.
Maybe some additional search criteria can be used? like special attribute?
On 11 June 2014 21:22, Alexei Fedotov <al...@gmail.com> wrote:
> Hi Brad,
>
> some segmentation already exists because only "some" users are allowed to
> use the app. If you don't want to segment the LDAP directory, you should
> segment some other information storage, e.g. remove LDAP authentication and
> use OM database for those who are allowed to participate.
>
>
>
> --
> With best regards / с наилучшими пожеланиями,
> Alexei Fedotov / Алексей Федотов,
> http://dataved.ru/
> +7 916 562 8095
>
> [1] Start using Apache Openmeetings today, http://openmeetings.apache.org/
> [2] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
> [3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
>
>
> On Wed, Jun 11, 2014 at 5:52 PM, LeBlanc, Brad A <bl...@tulane.edu>
> wrote:
>
>> We are currently using AD for our authentication for Openmeetings. All
>> of our users are in the same OU in our Active Directory. When any new
>> user, who’s a member of the Accounts OU, logs in for the first time, their
>> account is autocreated as a web user and grants them access to the public
>> rooms and their own private rooms. We don’t want all members of the
>> University to have access to this application. Is there a way to limit who
>> is authorized to access the application while using AD without segmenting
>> the OU?
>>
>>
>>
>> B. LeBlanc
>>
>>
>>
>
>
--
WBR
Maxim aka solomax
Re: Auto-Enrollment
Posted by Alexei Fedotov <al...@gmail.com>.
Hi Brad,
some segmentation already exists because only "some" users are allowed to
use the app. If you don't want to segment the LDAP directory, you should
segment some other information storage, e.g. remove LDAP authentication and
use OM database for those who are allowed to participate.
--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://dataved.ru/
+7 916 562 8095
[1] Start using Apache Openmeetings today, http://openmeetings.apache.org/
[2] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
[3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
On Wed, Jun 11, 2014 at 5:52 PM, LeBlanc, Brad A <bl...@tulane.edu>
wrote:
> We are currently using AD for our authentication for Openmeetings. All of
> our users are in the same OU in our Active Directory. When any new user,
> who’s a member of the Accounts OU, logs in for the first time, their
> account is autocreated as a web user and grants them access to the public
> rooms and their own private rooms. We don’t want all members of the
> University to have access to this application. Is there a way to limit who
> is authorized to access the application while using AD without segmenting
> the OU?
>
>
>
> B. LeBlanc
>
>
>