Grouper Users - Open Discussion List

["Biernath, Jutta" <>]

Hi,

 

sorry for my late response. Thank you for the patches! It seems to me that they are valid for Grouper 2.2 and higher, so I have translated them for our version (2.1.5). They work well.

 

Thanks a lot!

 

Jutta

 

--------------------

Jutta Biernath

Freie Universität Berlin

Zentraleinrichtung für Datenverarbeitung (ZEDAT)

Identity & Customer Management, FUDIS

Fabeckstr. 32

14195 Berlin

Tel. +49 30 838-75090

Fax +49 30 838-475090

 

Von: [mailto:] Im Auftrag von Chris Hyzer
Gesendet: Montag, 4. Mai 2015 07:23
An: David Langenberg; Biernath, Jutta
Cc: Gouper Users
Betreff: RE: [grouper-users] Problem with PSP if stem and group have equal names

 

I have two patches (one for api and ui) for v2.2.1 that has some hooks to solve this:

 

https://bugs.internet2.edu/jira/browse/GRP-1134

 

https://spaces.internet2.edu/display/Grouper/Unique+object+names+in+Grouper

 

Thanks,

Chris

 

 

From: [] On Behalf Of David Langenberg
Sent: Wednesday, April 29, 2015 1:17 PM
To: Jutta Biernath
Cc: Gouper Users
Subject: Re: [grouper-users] Problem with PSP if stem and group have equal names

 

Are you doing flat or bushy provisioning?  It sounds like bushy and for that I can think of two immediate fixes.  First change your provisioning to "flat" which will ensure proper uniqueness of names.  Second, write a Grouper Hook to keep the folder vs group names unique.  

 

Dave

 

On Wed, Apr 29, 2015 at 6:20 AM, Jutta Biernath <> wrote:

Hi,

some of our provisioned stems contain groups and stems with equal names, i.e.
for instance the stem "downloads" contains another stem "endnote" as well as a
group "endnote". We have not many, but several cases like that.

The problem is now that the PSP (version 2.1.5) doesn't seem to provision that
correctly. In a bulkSync the group is created and provisioned, but the stem
isn't. If the group is renamed (so that both have different names) the stem is
also provisioned. If then the group name is changed to the original name again
(so that both again have equal names) both are indeed provisioned, but the PSP
result on stdout shows an error, saying that the stem couldnt' be deleted due
to subordinate objects ([LDAP: error code 66 - subordinate objects must be
deleted first]).

As workaround we have renamed the groups to make sure both stem and group have
different names. But I think cases like that will also happen in the future
every now and then, therefore it would be great if a solution could be found.


Thank you,

Jutta Biernath

 

--

David Langenberg

Identity & Access Management Architect

The University of Chicago