[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xacml-users] AttributeSelector usage
nice discussion, >> We could not generalize the AttributeSelector, because it job is to >> select atomic values, not complex data structures. It would not be >> possible to define strict typing for arguments otherwise. You can >> access anything using an AttributeDesignator, from a context populated >> with your custom datatypes, or a function that returns your custom >> datatype and takes path to it as its argument, if you need to make >> selection as part of the policy. Such function would be responsible for >> the type safety then. Daniel, if i am getting your point correctly , u mean to have a function e.g. <Apply FunctionId="SECTINO: Extract-parameter-from-request"> <AttributeValue ="http://www.w3.org/2001/XMLSchema#string"> /Request/Action/Attribute[@AttributeID="p"]/AttributeValue/p/ID </AttributeValue> </Apply> in response the the request <Request> .. .. <Action> <Attribute AttributeId="urn:oasis:names:tc:xacml:1.0:attribute:p" DataType="http://www.w3.org/2001/XMLSchema#String"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#String"> <p> <iD>127Asbc </iD> . </p> </AttributeValue> </Attribute> </Action> .. .. </Request> The question is "why we need ResourceContent element at all i.e. If we can carry attribute values inside the request like given above." / Muhammad.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]