Return-Path: X-Original-To: apmail-incubator-openmeetings-user-archive@minotaur.apache.org Delivered-To: apmail-incubator-openmeetings-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 35E0F9114 for ; Wed, 4 Apr 2012 19:30:50 +0000 (UTC) Received: (qmail 29376 invoked by uid 500); 4 Apr 2012 19:30:50 -0000 Delivered-To: apmail-incubator-openmeetings-user-archive@incubator.apache.org Received: (qmail 29356 invoked by uid 500); 4 Apr 2012 19:30:50 -0000 Mailing-List: contact openmeetings-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: openmeetings-user@incubator.apache.org Delivered-To: mailing list openmeetings-user@incubator.apache.org Received: (qmail 29348 invoked by uid 99); 4 Apr 2012 19:30:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Apr 2012 19:30:50 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=FREEMAIL_REPLY,HTML_FONT_FACE_BAD,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rubens.queiroz@gmail.com designates 209.85.215.47 as permitted sender) Received: from [209.85.215.47] (HELO mail-lpp01m010-f47.google.com) (209.85.215.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Apr 2012 19:30:43 +0000 Received: by lagw12 with SMTP id w12so707037lag.6 for ; Wed, 04 Apr 2012 12:30:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=CefqZRYi9R5p1PglUYWIYQAv17JeVRIWHrvbI8xGywU=; b=abljXuIqxAm7nbeTiSBB5dZiU4q7BvCdaKGqb/LMkLL4bgGqKPTuYu4MZKxJ+C8TjL ChA9lHAof59MX7IJiAS7ECCenNPaGvF+0c8DoEBAjVyza4KZDjGfzANDio1WnaTEGQyH zbJPvFVpm1iPYF3tt8wPNYen36REBhTWwhQ6diyn2APOaqDSFRyOpv5krGwavKULis5H 5yfi/Cv07Qq5HdfozM1JQhxU5M4D4ulF6gaNC7/m9gayKeK7oNdmQR0QSNSuJN24Wz5E K84tLTYJJgMAabGsOitzT5YC6BM1krHq7dXwfkyMXhMTzBEWLaTuSgkec4E5e+6BQGxR Of2Q== MIME-Version: 1.0 Received: by 10.152.102.228 with SMTP id fr4mr20147960lab.23.1333567822175; Wed, 04 Apr 2012 12:30:22 -0700 (PDT) Received: by 10.112.85.67 with HTTP; Wed, 4 Apr 2012 12:30:22 -0700 (PDT) In-Reply-To: References: Date: Wed, 4 Apr 2012 16:30:22 -0300 Message-ID: Subject: Re: LDAP filter From: Rubens Queiroz de Almeida To: openmeetings-user@incubator.apache.org Content-Type: multipart/alternative; boundary=f46d040710ab531cc704bcdf74da X-Virus-Checked: Checked by ClamAV on apache.org --f46d040710ab531cc704bcdf74da Content-Type: text/plain; charset=ISO-8859-1 Dear Sebastian, In our university, we have three classes of records: staff, faculty and students. We would like to allow people belonging to the staff and faculty classes to be allowed access initially. So, we would like to fetch a name and associated information from our LDAP base, and upon arriving in Openmeetings we would check the field *EduPersonAffiliation*, which is an attribute with multiple values. Should it belong to either the faculty of staff class, access will be allowed. Thanks a lot, Rubens On Wed, Apr 4, 2012 at 4:23 PM, seba.wagner@gmail.com wrote: > How would you expect such a filter would look like? > Can't you add that to your ldap search base for the ou? > > Sebastian > Am 04.04.2012 20:43 schrieb "Rubens Queiroz de Almeida" < > rubens.queiroz@gmail.com>: > > Hi, >> >> I am using LDAP to authenticate user, but not all users are allowed to >> access the service. Is there a way to filter the information I get from >> LDAP so as to allow only authorized users? >> >> Thanks in advance, >> >> Rubens >> > --f46d040710ab531cc704bcdf74da Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dear Sebastian,

In our university, we have three classes of records: staff,= faculty and students. We would like to allow people belonging to the staff= and faculty classes to be allowed access initially. So, we would like to f= etch a name and associated information from our LDAP base, and upon arrivin= g in Openmeetings we would check the field=A0EduPersonAffiliation, w= hich is an attribute with multiple values. Should it belong to either the f= aculty of staff class, access will be allowed.

Thanks = a lot,

Rubens



On Wed, Apr 4, 2012 at 4:23 PM, seba.wagner@gmail.com <seba.wagner@gmail.com>= wrote:

How would you expect such a filter would = look like?
Can't you add that to your ldap search base for the ou?

Sebastian

Am 04.04.2012 20:43 schrieb "Rubens Queiroz= de Almeida" <rubens.queiroz@gmail.com>:

Hi,

I am using LDAP to authenticate user, = but not all users are allowed to access the service. Is there a way to filt= er the information I get from LDAP so as to allow only authorized users?

Thanks in advance,

Rubens<= /font>

--f46d040710ab531cc704bcdf74da--