Grouper Developers Forum

[Chris Hyzer <>]

 

>

>

> Yes, you can query based on the group name or the uuid.  Right now the API expects you to pass a uuid. 

> But since the history includes the group names, you can get all the uuids associated with a group name.  Depending on what we want, I'll adjust the API.

>

 

Great, thanks

 

> So if a member search is done by group name and there have been multiple groups with that name, there are a couple of things to think about I think...

>

> 1.  Security for the prior group.  I'm not sure it makes much sense to look at the privileges of the current group (if one even exists now) or the

> privileges of the prior group (right before it was deleted?) to determine who can read members of the prior group.  I suppose we could assume

> you have to be a wheel member or GrouperSystem.

 

Sounds good

 

>

> 2.  Since the two groups have different uuids, it seems like we would want two different wsGroup objects in the resulting XML and associate

> the correct subjects with the correct wsGroup.  For Get Members Rest Lite, I don't see a good way to have multiple wsGroup objects in the

> output without changing the schema of the output.  Though I think this can be done in the non-Lite version by just having multiple instances

> of WsGetMembersResult.

>

 

Well, the lite method could require a group UUID, and just return one set of results…   maybe if you pass a group name it works for the latest group (if deleted or recreated)…  tradeoff between ease of use and consistency…

 

>

> Currently, there's a GSH method to delete old point in time records based on a time.   I'll add more methods to take care of the cases you've

> mentioned and just document that it can make the history wrong if the groups are used elsewhere.

>

 

Great, thanks.

 

> Sounds like Jim is voting for read privilege, so I'll go with that unless anybody disagrees. 

>

 

Sounds good.