authorization - XACML Obligations -
how use obligations in xacml? reference helpful scenario obligations should refer pip , retrun result pep
thanks
---edit--- example author's comment:
<obligationexpressions> <obligationexpression obligationid="emailobligation" fulfillon="permit"> <attributeassignmentexpression attributeid="urn:oasis:names:tc:xacml:3.0:example:attribute:text"> <attributedesignator mustbepresent="false" category="urn:oasis:names:tc:xacml:1.0:subject-category:access-subject" attributeid="urn:oasis:names:tc:xacml:1.0:subject:subject-id" datatype="w3.org/2001/xmlschema#string"/> </attributeassignmentexpression> </obligationexpression> </obligationexpressions>
obligations in xacml (as advice introduced in xacml 3.0) used enrich authorization flow.
a typical xacml response bears decision (either of permit, deny, not applicable, or indeterminate). but, if want tell user why access denied? if want implement "break glass" scenario?
this obligations , advice come in handy. here few examples:
- deny alice access document d + obligation: email manager, bob, let him know alice tried access document d.
- deny doctor house right view medical record + obligation: tell doctor house can "break glass" access medical record.
- allow joe view document d first watermark document before returning joe
in xacml 3.0 obligations , advice can have variable parts such - in examples above - manager's email. parts can retrieved pip.
Comments
Post a Comment