Grouper Developers Forum

[Chris Hyzer <>]

Ø  Do you think it might make sense to only look at groups, stems, and attributes that currently exist for these queries?  So for instance, say a group was created on 1/1/2010 that had some memberships and was deleted after a few days.  Then a group (different uuid but same name) got added on 1/1/2011 possibly by somebody else.  If a point in time query is made for all memberships of the group (based on a group name query) that existed on or before 1/2/2011, should that ignore the ones from the prior group that was deleted? 

 

Hmmm…. That is up to you.  I guess the most correct thing to do is to look at any groups with that name at any point in time.  It’s a little confusing since you can lookup a group by uuid or name in the WS.  I didn’t mention this in the wiki, but if you get members on a group which doesn’t currently exist, the lookup will barf.  So either we need the WsGroupLookup logic that does the lookup to look at grouper history if it is a point in time query, or it just need to pass the UUID or name to the API method.   Maybe we should start by discussing the API.  Is there a wiki on this?  A search doesn’t find it…  i.e. is there a way to get point in time members based on group name, which would behave differently than doing it by uuid?  Ie. by uuid it would get just that group while it exists and is deleted.  If created again it would have a new UUID… but name would get all of them.

 

Also, you and I talked about this before, so I thought I would mention again… if some grouper user does some load testing, it will fill up the point in time with junk… I think it would be nice to have a GSH method to be able to remove things from point in time.  i.e. remove a group or some memberships or whatever.  Granted this might make other things not correct, but I think it is up to the Grouper deployer to decide… i.e. if there is a test stem, and you remove it from point in time, then you assume that no real groups use those test groups and need the history…  I think we ended our last discussion by saying that we wouldn’t be able to delete, but I keep thinking we need this feature once the DBA complain that too much space is being used…

 

Ø  Also, I'm assuming for security that you have to be a current admin of the group.

 

That’s fine with me if its fine with everyone else, as opposed to READ privilege…

Thanks,

Chris

 

From: Shilen Patel [mailto:]
Sent: Friday, January 07, 2011 1:23 PM
To: Chris Hyzer
Cc:
Subject: Re: point in time web services

 

OK thanks Chris.  I'll start with getMembers and see where that takes me. 

Do you think it might make sense to only look at groups, stems, and attributes that currently exist for these queries?  So for instance, say a group was created on 1/1/2010 that had some memberships and was deleted after a few days.  Then a group (different uuid but same name) got added on 1/1/2011 possibly by somebody else.  If a point in time query is made for all memberships of the group (based on a group name query) that existed on or before 1/2/2011, should that ignore the ones from the prior group that was deleted?  Also, I'm assuming for security that you have to be a current admin of the group.

Thanks!

-- Shilen


On 1/7/11 12:30 PM, Chris Hyzer wrote:

Shilen, lets talk point in time web services.

I picture it as augmenting the existing web services to include point in time params…  I think we discussed that before.

 

Which operations should take these as inputs? 

 

These are the readonly WS queries: findGroups,  findStems, getAttributeAssignments, getGrouperPrivileges, getGroups, getMembers, getMemberships, getPermissionAssignments, hasMember  

 

I think the findGroups and findStems ones would be hard, though maybe you know better.

 

Maybe we could start with these:  getGroups, getMembers, hasMember

 

Maybe the first one is getMembers.

 

Up to you.

 

I made a wiki about how to augment a Grouper Web Services (e.g. for point in time).

 

https://spaces.internet2.edu/display/Grouper/Grouper+Web+Services+for+developers

 

Anyways, let me know when you commit stuff so I can review, and update that wiki if I missed something (there are a lot of steps, Im sure I missed some J )

 

Also, I bet we could pretty easily augment the lite UI to have an option under the “advanced” button so two timestamp fields appear and you could see the list (or I guess also export) based on point in time.  If you are interested in that let me know and we can work on it together or I could make a similar doc about it for you to work on it… J

 

Thanks,

Chris

 

 

From: [] On Behalf Of Emily Eisbruch
Sent: Thursday, January 06, 2011 2:59 PM
To: Grouper Dev
Subject: [grouper-dev] Action Items: Grouper Call 5-Jan-2011

 

New Action Items

 

[AI] ( Rob) will continue to investigate the viability of a Grouper VM. 

 

[AI] (TomZ) will inform AnnKW which LDAPPC and which LDAPPC-ng wiki pages are product versus development. 

 

[AI] (Ann KW) will move the appropriate development pages in the wiki to project pages in the wiki.

 

[AI] (AnnKW) will look at queries of the Grouper wiki to be sure there are no outdates pages.

 

[AI] (Shilen and Chris) will talk about point in time web services.

 

Carry Over Action Items

 

[AI] (TomZ) will report on timing for Grouper demo work. 

 

[AI] (TomZ) will create a wiki page enumerating activities related to connectors. 

 

[AI] (TomZ) will work with Chad in the process of proposing a Working Group to focus on provisioning.

 

[AI] (TomZ and Chris) will discuss/work on LDAP Grouper Loader for importing groups. JIRA 442  

 

[AI] (Everyone) review Rob's chapters and give him feedback on the Grouper Users List.https://spaces.internet2.edu/display/GrouperWG/GrouperBook   

 

[AI] (TomB) will explore new international participation for work on the Grouper UI. 

 

 [AI] (Emily) will give suggestions to Ann KW on the community contributions page of wikihttps://spaces.internet2.edu/display/Grouper/Contributions 

 

 

 

Emily Eisbruch, Technology Transfer Analyst

Internet2

office: +1-734-352-4996 | mobile +1-734-730-5749

 

Visit our website: www.internet2.edu
Follow us on Twitter: www.twitter.com/internet2
Become a Fan on Facebook: www.internet2.edu/facebook