Next in thread →
Next in month →
Re: [xacml] Re: "else" is what ? Was:Re: [xacml] Generalizing on-permit-apply-second
I stand corrected. My reticence to having an if/then construct remains, but I seem alone in this position so I will refrain from pursuing further. b On May 24, 2013, at 9:41 AM, Danny Thorpe <> wrote: > Order of policy processing is already imposed by the existing Ordered-Deny-Overrides, Ordered-Permit-Overrides, and First-Applicable policy combining algorithms. > > -Danny > > Danny Thorpe > Authorization Architect > Dell | Identity & Access Management > > Quest Software is now part of Dell. > >> -----Original Message----- >> From: [mailto:] On >> Behalf Of Bill Parducci >> Sent: Thursday, May 23, 2013 10:30 PM >> To: Steven Legg >> Cc: Erik Rissanen; >> Subject: Re: [xacml] Re: "else" is what ? Was:Re: [xacml] Generalizing on- >> permit-apply-second >> >> >> On May 23, 2013, at 6:05 PM, Steven Legg <> >> wrote: >> >>>> Ok. So to make sure that I am fully grasping this, the proposal is >>>> that this new mechanism only applies to PolicySets (not Policies) >>> >>> Correct. The on-permit-apply-second combining algorithm is only >>> defined as a policy combining algorithm. >>> >>> and that these PolicySets will have a new requirement that Policy order is >> required to be maintained within them. Is this correct? >>> >>> Yes, the order is significant (even in the current draft). >> >> Thanks Steven. I believe this marks a bit of a shift in our approach as it the >> first situation where there is different processing logic between Policy and >> PolicySet and the requirement for order of Policy processing. >> >> b >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis- >> open.org/apps/org/workgroup/portal/my_workgroups.php >
Next in thread →
Next in month →