Maybe some additional search criteria can be used? like special attribute?
On 11 June 2014 21:22, Alexei Fedotov <alexei.fedo...@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 <blebl...@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
