Grouper Users - Open Discussion List

["Jason B. Rappaport" <>]

Thank you everyone for the feedback!

 

I created an intersection group of NextGeneration_Users_Allow and NextGenration_Users_Deny and found there is one member in that group….so the math does make sense when you do it correctly. 

 

Thanks again, Jay

 

 

 

________________________________

Jason Rappaport

Identity and Access Management Analyst

Office of Information Technology

Email: 

Office:  609-258-8464

 

From: <> On Behalf Of Redman, Chad
Sent: Thursday, June 27, 2019 9:22 AM
To:
Subject: RE: [grouper-users] Math in visualizer

 

Hmm, sounds like it would be useful to add a feature to show which members are actually excluded by the complement. And maybe another one to show which users are excluded because they aren't in the second factor of an intersect?

 

From: [] On Behalf Of Jeffrey Williams
Sent: Thursday, June 27, 2019 9:10 AM
To: Robert Bradley <>
Cc: Grouper-Users <>
Subject: Re: [grouper-users] Math in visualizer

 

 

 

| Maybe one of you deny’s are not in the allow’s?  So only one is
| subtracted?  Compare the subjectId of owner, and each factor to
| see for sure 😊
|

That was my guess as well, but Jason will have to comment on that
himself. :)

 

Correct me if I'm wrong, but I think the quickest way to find out is to change NextGenerationUsers' type of composite to an intersect(AND) and see how many members are both in allow and deny.  That will be your true operand to subtract from the NextGeneration_Users_allow.

 

 

 

--

Jeffrey Williams 

Identity Engineer
Identity & Access Services
https://its.uncg.edu

 

Attachment: smime.p7s
Description: S/MIME cryptographic signature