LDAP group filter

[Elestedt, Fredrik]

Hi,

I'm doing a quick investigation of LDAP support in different artifact management system and at the moment I'm investigating Archiva.
I've set up an instance and successfully configured the LDAP backend to work against our test environment LDAP, but I've run in to an
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 group
search result? I found one for users - but that I don't want to filter.

// Fredrik

[Fabian Trampusch]

You can use the baseDn for groups to filter the displayed groups.

We use something like this:
ou=maven,dc=isys-software,dc=de

The difference between your and our setup is probably, that we have an
own organizational unit for the maven groups.

(I am not the one who administrates LDAP in our company, therefore i can
not provide experience if this is a beneficial approach)

Regards
Fabian

Post by Elestedt, Fredrik
Hi,
I'm doing a quick investigation of LDAP support in different artifact management system and at the moment I'm investigating Archiva.
I've set up an instance and successfully configured the LDAP backend to work against our test environment LDAP, but I've run in to an
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 group
search result? I found one for users - but that I don't want to filter.
// Fredrik

[Elestedt, Fredrik]

Hi,

Unfortunantly that won't do it.
It's not a group filter - it's just placing all groups in a OU in LDAP, which I can't change.
I have to provide a search filter somewhere, such as (& (objectClass=groupOfNames) (owner=...) )

// Fredrik

-----Original Message-----
From: Fabian Trampusch [mailto:***@isys-software.de]
Sent: den 19 augusti 2015 15:40
To: ***@archiva.apache.org
Subject: Re: LDAP group filter

You can use the baseDn for groups to filter the displayed groups.

We use something like this:
ou=maven,dc=isys-software,dc=de

The difference between your and our setup is probably, that we have an own organizational unit for the maven groups.

(I am not the one who administrates LDAP in our company, therefore i can not provide experience if this is a beneficial approach)

Regards
Fabian

Post by Elestedt, Fredrik
Hi,
I'm doing a quick investigation of LDAP support in different artifact management system and at the moment I'm investigating Archiva.
I've set up an instance and successfully configured the LDAP backend
to work against our test environment LDAP, but I've run in to an 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 group search result? I found one for users - but that I don't want to filter.
// Fredrik

[Mat P Jaggard]

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
the Java LDAP implementation. We only actually want 2 groups which we
could filter on.

Is there any way around this problem?

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

Date: 20/08/2015 07:03
Subject: RE: LDAP group filter
Hi,
Unfortunantly that won't do it.
It's not a group filter - it's just placing all groups in a OU in
LDAP, which I can't change.
I have to provide a search filter somewhere, such as (&
(objectClass=groupOfNames) (owner=...) )
// Fredrik
-----Original Message-----
Sent: den 19 augusti 2015 15:40
Subject: Re: LDAP group filter
You can use the baseDn for groups to filter the displayed groups.
ou=maven,dc=isys-software,dc=de
The difference between your and our setup is probably, that we have
an own organizational unit for the maven groups.
(I am not the one who administrates LDAP in our company, therefore i
can not provide experience if this is a beneficial approach)
Regards
Fabian

Post by Elestedt, Fredrik
Hi,
I'm doing a quick investigation of LDAP support in different

artifact management system and at the moment I'm investigating Archiva.

Post by Elestedt, Fredrik
I've set up an instance and successfully configured the LDAP backend
to work against our test environment LDAP, but I've run in to an 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

group search result? I found one for users - but that I don't want to

filter.

Post by Elestedt, Fredrik
// Fredrik