Grouper Users - Open Discussion List

[Shilen Patel <>]

The first uuid is the group id and the second is the member id.  So you
can do the following in gsh:

Group group = 
GrouperDAOFactory.getFactory().getGroup().findByUuid("63f2036200ff48d48aa46
3e33ca43622", true);
Member member = 
GrouperDAOFactory.getFactory().getMember().findByUuid("5ec8735b43f546d08061
ca33a73a4964", true);

group.getName()

member.getSubjectId()


Or if you run bad membership finder via gsh, it'll print out those
translations.


Thanks!

- Shilen



On 10/18/16, 12:47 PM, "Waldbieser, Carl" 
<>
 wrote:

>Chris,
>
>I meant, "is there an easy way to translate the UUIDs into something that
>makes sense to me?"  So I can look at something like:
>
>  
>GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_cre
>ateNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
>"5ec8735b43f546d08061ca33a73a4964", "612e954d58c44e37985e4e6fbb0f3b9a"));
>
>And translate it into something like: "This will add subject 'waldbiec'
>to group 'network-overlords'."
>I'm not looking for something that translates into human language-- just
>something to spit out what the proposed action is, and translate the
>group and subject names if possible.
>
>Thanks,
>Carl
>
>----- Original Message -----
>From: "Hyzer, Chris" 
><>
>To: "waldbiec" 
><>,
> "Kumi Hagimoto"
><>
>Cc: 
>
>Sent: Tuesday, October 18, 2016 12:37:17 PM
>Subject: RE: Composite with complement did not update?
>
>There is no bad-badmembershipfinder-finder... that is the correct script.
> And note, you should run it again afterwards until it says things are
>good.
>
>Note, 2.3 api patch 23: find bad memberships daemon
>
>https://urldefense.proofpoint.com/v2/url?u=https-3A__spaces.internet2.edu_
>display_Grouper_v2.3-2BRelease-2BNotes&d=CwIFaQ&c=imBPVzF25OnBgGmVOlcsiEgH
>oG1i6YHLR0Sj_gZ4adc&r=sWqutME58phurE0oO57Icg&m=jpTcJqYFzK_VZSFeDoygi8UB9U3
>i5t9sDP0ilULP6DQ&s=rHnLszS1rDxMqFC5YOe6mDDhCckvYuQHGL4dhRGLVwA&e=
>https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.internet2.edu_ji
>ra_browse_GRP-2D1367&d=CwIFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4ad
>c&r=sWqutME58phurE0oO57Icg&m=jpTcJqYFzK_VZSFeDoygi8UB9U3i5t9sDP0ilULP6DQ&s
>=IbLjZicVJYMeMEu9jXslJJRwDiVmvqk8bY0et2vNnFc&e=
>
>This will run automatically so you don¹t need to worry about it.
>
>Thanks
>Chris
>
>-----Original Message-----
>From: 
>
>[mailto:]
> On Behalf Of Waldbieser, Carl
>Sent: Tuesday, October 18, 2016 12:28 PM
>To: Kumi Hagimoto 
><>
>Cc: 
>
>Subject: Re: [grouper-users] Composite with complement did not update?
>
>Kumi,
>
>That does look to be what happened.
>When I run the bad membership finder, I get an output script with a
>number of statements that I'm not sure what they are doing:
>
>    GrouperSession.startRootSession();
>    
>GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_cre
>ateNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
>"5ec8735b43f546d08061ca33a73a4964", "612e954d58c44e37985e4e6fbb0f3b9a"));
>    
>GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_cre
>ateNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
>"892bc28297f94372a5179eeec548c63e", "612e954d58c44e37985e4e6fbb0f3b9a"));
>    
>GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_cre
>ateNewCompositeMembershipObject("71f7aba21f3948399727c4ec33fd3c1e",
>"9aa9723ce7df4025a68c91d9450c6371", "0c354eb1eef74201a383b515d8b456bb"));
>    
>GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_cre
>ateNewCompositeMembershipObject("71f7aba21f3948399727c4ec33fd3c1e",
>"faf83a9bac5e4832adc38ab64f4e6427", "0c354eb1eef74201a383b515d8b456bb"));
>    
>GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_cre
>ateNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
>"faf83a9bac5e4832adc38ab64f4e6427", "612e954d58c44e37985e4e6fbb0f3b9a"));
>    
>GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_cre
>ateNewCompositeMembershipObject("71f7aba21f3948399727c4ec33fd3c1e",
>"fdaf8e85ee264f3eb83be6ced20276f1", "0c354eb1eef74201a383b515d8b456bb"));
>    
>GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_cre
>ateNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
>"fdaf8e85ee264f3eb83be6ced20276f1", "612e954d58c44e37985e4e6fbb0f3b9a"));
>    sqlRun("delete from grouper_memberships where
>id='7a2e3a0e7365426a9b2c73602b3f99c2'");
>    sqlRun("delete from grouper_memberships where
>id='d3f6b104d5ab4a959e62dbec06d46a46'");
>
>The last 2 seem to be removing some obsolete groups.
>Are the `Composite.internal_createNewCompositeMembershipObject` creating
>missing memberships?  Is there some way to (easily) check these before
>updating?
>
>Thanks,
>Carl
>
>----- Original Message -----
>From: "Kumi Hagimoto" 
><>
>To: 
>,
> "waldbiec" 
><>
>Sent: Tuesday, October 18, 2016 11:58:47 AM
>Subject: Re: [grouper-users] Composite with complement did not update?
>
>Hi Carl,
>
>Looks like maybe you're seeing the same issue we have with v2.2.1?
>
>https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.internet2.edu_s
>ympa_arc_grouper-2Dusers_2016-2D09_msg00033.html&d=CwIFaQ&c=imBPVzF25OnBgG
>mVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=sWqutME58phurE0oO57Icg&m=jpTcJqYFzK_VZSFeD
>oygi8UB9U3i5t9sDP0ilULP6DQ&s=tchPQYkDlx8sk1ctoTg-fztoKYsuqNGf0ivQ8-D7yYY&e
>= 
>
>We just run the BadMembership gsh generated by nightly report until we
>upgrade.
>
>Thanks,
>Kumi