Structure of delegation evidence
Last updated
Last updated
This page describes (and prescribes) how, in data spaces/iSHARE network, delegation is communicated between different parties.
In data spaces/iSHARE network, delegation evidence expresses the delegation of rights from a delegator (the party that delegates rights; the policyIssuer) to the delegate (the party that receives the delegated rights; i.e. the accessSubject). Rights are expressed in rules in terms of allowed actions to be performed on resources, under the license(s) as defined in policySets.
Delegation evidence is modelled as a JSON object inspired by the XACML 3.0 specifications and structured as follows:
The root delegationEvidence element contains the following parameters.
delegationEvidence
{ }
Yes
The root of any delegation evidence
notBefore
delegationEvidence
int
Yes
Unix timestamp in UTC indicating the start of validity period of this delegation evidence. SHOULD equal the time of issuing of the evidence unless historic evidence is requested.
notOnOrAfter
delegationEvidence
int
Yes
Unix timestamp in UTC indicating the end of validity period of this delegation evidence. It is up to the issuer off the evidence to set this time. Note that a reasonable amount of time SHOULD be allowed for processing of longer delegation paths. Also note that evidence cannot be revoked, so setting very long validity periods SHOULD be avoided.
policyIssuer
delegationEvidence
string
Yes
target
delegationEvidence
{ }
Yes
MUST for the root level contain an accessSubject. No other elements are allowed. It makes the entire delegation evidence applicable only to this accessSubject.
accessSubject
target
string
Yes
policySets
delegationEvidence
[ ]
Yes (1..n)
Container for one or more objects containing policy elements with an indication for further delegation. Note that policySet elements within one delegationEvidence MUST not restrict each other, but rather offer a mechanism to express additional rights. They MUST be evaluated in a "permit-override" manner, allowing a "Permit" if only one of the policySet elements evaluates to "Permit".
The second level objects in policySets each contain the following parameters. Other parameters are not allowed. Note that XACML spec is heavily restricted, a.o. for the reason to prevent redundancy (and resulting possible conflicts) with the root policySet element.
maxDelegationDepth
policySets
int
No
Optional element that, if present, indicates that further delegation of the rights, conveyed in the policy elements that are part of this PolicySet, is allowed. The value indicates the delegation steps that are allowed after this step in order to evaluate the entire delegation path to "Permit"
target
policySet
{ }
Yes
environment
target
{ }
Yes
licenses
environment
[ ]
Yes
policies
policySets
[ ]
Yes (1..n)
Used to express the actual rights being delegated. Note that policies within one policySets object MUST not restrict each other, but rather offer a mechanism to express additional rights. They MUST be evaluated in a "permit-override" manner, allowing a "Permit" if only one of the policy elements evaluates to "Permit".
A Policy element contains the following parameters.
target
policies
string
Yes
Describes the target, in terms of resource and action, this policy applies to. It is also the scope that is permitted through the default Rule. Additional Rule elements can be described to exclude Resources and Actions from the default policy rights
resource
target
{ }
Yes
type
resource
string
Yes
identifiers
resource
[ ]
Yes
Array of strings containing one or more resource identifiers. Depending on the Type an identifier SHOULD be a urn.
attributes
resource
[ ]
No
Optional array of attributes of the resources the delegated rights apply to. If omitted defaults to all attributes. Depending on the Type an attribute SHOULD be a urn.
actions
target
[ ]
Yes
environment
target
{ }
No
serviceProviders
environment
[ ]
No
Optional array which lists the iSHARE client ID's of serviceProviders which are allowed to provide services to the accessSubject as described within this policy.
rules
policies
[ ]
Yes (1..1)
Contains one Rule element.
The Rule element contains the following parameters.
effect
rules
string
Yes
Contain 'Permit' or 'Deny', as the outcome of Authorization Registry logic.
Additional Rule elements contains the following parameters.
Example delegation JSON:
The JSON object consists of a root delegationEvidence element (modeled after an XACML PolicySet element) containing one or more policySet objects in the policySets array. The root element is only meant as a container element and extends the XACML specifications to cater for some iSHARE required metadata such as timestamps. Each of the second level policySet elements only acts as a container for actual policy elements with an indication of the rights in this policySet can be further delegated (with maxDelegationDepth) and what do apply. No other delegation logic is conveyed a second level policySet. Each policy element is used to express the actual rights being delegated.
of the delegator (the delegating entity)
of the delegate (the entity that receives the delegated rights)
Array which describes which apply to this policySet.
String which describes the type of resource to which the rules apply. The use of the type "iSHARE.DELEGATION" is reserved for .
