Mailing-List: contact users-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@archiva.apache.org
Message-Id: <201510191526.t9JFQKrd014820@d06av03.portsmouth.uk.ibm.com>
In-Reply-To: 
 <743FFC0146BAB3439F30545F1EA08E5222A6A4ED@DB4PRD4001MB032.050d.mgd.msft.net>
To: users@archiva.apache.org
Subject: RE: LDAP group filter
From: "Mat P Jaggard" <mat@uk.ibm.com>
Date: Mon, 19 Oct 2015 16:25:24 +0100
References: 
 <743FFC0146BAB3439F30545F1EA08E5222A6A228@DB4PRD4001MB032.050d.mgd.msft.net>
 <55D48712.6090302@isys-software.de>
 <743FFC0146BAB3439F30545F1EA08E5222A6A4ED@DB4PRD4001MB032.050d.mgd.msft.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="=_alternative 0054B8C580257EE3_="

--=_alternative 0054B8C580257EE3_=
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="US-ASCII"

We have the same problem. A long delay while the massive list of groups is =

downloaded, followed by an array list out of bounds exception from within=20
the Java LDAP implementation. We only actually want 2 groups which we=20
could filter on.

Is there any way around this problem?

Mat Jaggard
Java Developer
Enterprise Content Management / Software Group / IBM UK

"Elestedt, Fredrik" <fredrik.elestedt@volvocars.com> wrote on 20/08/2015=20
07:03:58:

> From: "Elestedt, Fredrik" <fredrik.elestedt@volvocars.com>
> To: "users@archiva.apache.org" <users@archiva.apache.org>
> Date: 20/08/2015 07:03
> Subject: RE: LDAP group filter
>=20
> Hi,
>=20
> Unfortunantly that won't do it.
> It's not a group filter - it's just placing all groups in a OU in=20
> LDAP, which I can't change.
> I have to provide a search filter somewhere, such as (&=20
> (objectClass=3DgroupOfNames) (owner=3D...) )
>=20
> // Fredrik
>=20
> -----Original Message-----
> From: Fabian Trampusch [mailto:fabian.trampusch@isys-software.de]=20
> Sent: den 19 augusti 2015 15:40
> To: users@archiva.apache.org
> Subject: Re: LDAP group filter
>=20
> You can use the baseDn for groups to filter the displayed groups.
>=20
> We use something like this:
> ou=3Dmaven,dc=3Disys-software,dc=3Dde
>=20
> The difference between your and our setup is probably, that we have=20
> an own organizational unit for the maven groups.
>=20
> (I am not the one who administrates LDAP in our company, therefore i
> can not provide experience if this is a beneficial approach)
>=20
> Regards
> Fabian
>=20
> Am 19.08.2015 um 08:57 schrieb Elestedt, Fredrik:
> > Hi,
> >
> > I'm doing a quick investigation of LDAP support in different=20
> artifact management system and at the moment I'm investigating Archiva.
> > I've set up an instance and successfully configured the LDAP backend=20
> > to work against our test environment LDAP, but I've run in to an=20
issue.
> >
> > Archiva loads up all groups - not just the ones which are pertinent to =


> > Archiva. Is there an option somewhere I can set to filter the=20
> group search result? I found one for users - but that I don't want to=20
filter.
> >
> > // Fredrik
> >
>=20
>=20


--=_alternative 0054B8C580257EE3_=--