Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

Yes, the bad membership finder fixes the database primitives and does not use 
the API which triggers audit log changes.

-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Dave Churchley
Sent: Thursday, January 25, 2018 11:00 AM
To: Waldbieser, Carl 
<>;
 grouper-users 
<>
Subject: [grouper-users] RE: Bad membership finder and audit logs

Hi Carl

As I understand it (I may well be wrong!), the audit log only shows direct 
membership changes. I think the bad membership finder would be tidying up 
indirect memberships and so you wouldn't see anything in the audit log.

Cheers
Dave

>-----Original Message-----
>From: 
>
> [
>]
> On Behalf Of Waldbieser, Carl
>Sent: 25 January 2018 15:51
>To: grouper-users 
><>
>Subject: [grouper-users] Bad membership finder and audit logs
>
>
>In Grouper 2.2, if I use the findBadMemberships option to correct bad
>memberships, would that be visible in the audit logs for a group?
>
>E.g.
>
>Grouper loader runs at midnight, a subject is pulled out of one reference
>group and placed in another, both of which feed into the same policy.
>Because of some timing quirk, the membership is not reflected in the final
>policy.
>
>Later, around 7am, the membership fixer script runs.  The memberships are
>corrected for the policy.
>
>If I view the audit log for the policy, will I see that a change happened at
>midnight and again at 7am?  Or will I see only one change?  Or no changes?
>
>Thanks,
>Carl Waldbieser
>ITS Identity Management
>Lafayette College