使用 XACML 来表达策略，这是一个逻辑表达式 [英] Using XACML to express policy which is a logical expression
问题描述
我对 XACML 很陌生.我正在使用 XACML 来表达策略.但除了 OASIS XACML 技术委员会.
I am very new to XACML. And I am using XACML to express policy. But I can't find any good examples except a few from the OASIS XACML Technical Committee.
好的，这是我的问题:
我想使用 XACML 来表达策略.用户只有满足策略才能访问资源.策略是一个逻辑表达式.例如:
I want to express policy using XACML. Users can access to the resources only if they satisfy the policy. The policy is an logical expression. For example:
(not A1) and (A2 OR A3) and (2 of (A4, A5,A6))
(not A1) and (A2 OR A3) and (2 of (A4, A5,A6))
(A4,A5,A6) 中的 2 表示仅当 A4,A5,A6 中的 2 个或更多为真时才为真.
2 of (A4,A5,A6) refers that it is true only if 2 or more of A4,A5,A6 is true.
AllOf"和AnyOf"可以用来表达AND"和OR"，但是我不知道如何表达2 of (A4,A5,A6)"和not A1".
"AllOf" and "AnyOf" can be used to express "AND" and "OR", but I don't know how to express "2 of (A4,A5,A6)" and "not A1".
谢谢！
推荐答案
根据您的需求，您需要使用 XACML 条件.条件仅存在于规则中，因此这意味着您必须将逻辑置于规则中.
Based on the requirement you have, you need to use a XACML condition. Conditions live within rules only so this means you'll have to put your logic inside the rule.
这是因为您将需要一个 XACML 目标中不允许的函数:n-of.
This is because you will need a function not allowed in XACML targets: n-of.
这也是因为 XACML 目标不能有否定表达式.表达 Not(A1) 的唯一方法是通过条件.
This is also because a XACML Target cannot have negative expressions. The only way you can express Not(A1) is via a condition.
这样做的原因是 XACML 处理属性包.所以当你写一个目标时:
The reason for that is that XACML deals with attribute bags. So when you write in a target:
role==manager
你实际上是在说:如果用户至少有一个相当于经理的角色......
What you are in fact saying is: if the user has at least one role equal to manager...
那么相反的会是什么?
对于 (a,b,c) 中的 2，您可以使用名为 n-of 的 XACML 函数(urn:oasis:names:tc:xacml:1.0:function:n-of 定义在 A.3.5 逻辑函数)
With respect to your 2 of (a,b,c), you can use the XACML function called n-of (urn:oasis:names:tc:xacml:1.0:function:n-of defined in A.3.5 Logical functions)
结果在 ALFA
/**
* (not A1) and (A2 OR A3) and (2 of (A4, A5,A6))
*/
policy stackoverflow{
apply firstApplicable
rule so{
condition not(A1=="some value") && (A2=="" || A3=="") && nOf(2, stringOneAndOnly(A4)=="value", stringOneAndOnly(A5)=="value", stringOneAndOnly(A6)=="value")
permit
}
}
在上面的示例中，我使用 A1 到 A6 字符串属性而不是布尔值来显示如何与值进行比较.请注意，我必须使用 stringOneAndOnly 函数来确保 nOf 函数中使用的每个属性都有一个值.
In the example above I made A1 through A6 string attributes instead of boolean to show how you would compare with values. Note that I have to use the stringOneAndOnly function to make sure there is a single value for each of the attributes used in the nOf function.
XACML 输出如下:
The XACML output is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!--This file was generated by the ALFA Plugin for Eclipse from Axiomatics AB (http://www.axiomatics.com).
Any modification to this file will be lost upon recompilation of the source ALFA file-->
<xacml3:Policy xmlns:xacml3="urn:oasis:names:tc:xacml:3.0:core:schema:wd-17"
PolicyId="http://axiomatics.com/alfa/identifier/policing.principles.stackoverflow"
RuleCombiningAlgId="urn:oasis:names:tc:xacml:1.0:rule-combining-algorithm:first-applicable"
Version="1.0">
<xacml3:Description>(not A1) and (A2 OR A3) and (2 of (A4, A5,A6))</xacml3:Description>
<xacml3:PolicyDefaults>
<xacml3:XPathVersion>http://www.w3.org/TR/1999/REC-xpath-19991116</xacml3:XPathVersion>
</xacml3:PolicyDefaults>
<xacml3:Target />
<xacml3:Rule
Effect="Permit"
RuleId="http://axiomatics.com/alfa/identifier/policing.principles.stackoverflow.so">
<xacml3:Description />
<xacml3:Target />
<xacml3:Condition>
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:and">
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:not" >
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:any-of">
<xacml3:Function FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-equal"/>
<xacml3:AttributeValue
DataType="http://www.w3.org/2001/XMLSchema#string">some value</xacml3:AttributeValue>
<xacml3:AttributeDesignator
AttributeId="A1"
DataType="http://www.w3.org/2001/XMLSchema#string"
Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource"
MustBePresent="false"
/>
</xacml3:Apply>
</xacml3:Apply>
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:and">
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:or">
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:any-of">
<xacml3:Function FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-equal"/>
<xacml3:AttributeValue
DataType="http://www.w3.org/2001/XMLSchema#string"></xacml3:AttributeValue>
<xacml3:AttributeDesignator
AttributeId="A2"
DataType="http://www.w3.org/2001/XMLSchema#string"
Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource"
MustBePresent="false"
/>
</xacml3:Apply>
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:any-of">
<xacml3:Function FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-equal"/>
<xacml3:AttributeValue
DataType="http://www.w3.org/2001/XMLSchema#string"></xacml3:AttributeValue>
<xacml3:AttributeDesignator
AttributeId="A3"
DataType="http://www.w3.org/2001/XMLSchema#string"
Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource"
MustBePresent="false"
/>
</xacml3:Apply>
</xacml3:Apply>
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:n-of" >
<xacml3:AttributeValue
DataType="http://www.w3.org/2001/XMLSchema#integer">2</xacml3:AttributeValue>
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-equal">
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-one-and-only" >
<xacml3:AttributeDesignator
AttributeId="A4"
DataType="http://www.w3.org/2001/XMLSchema#string"
Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource"
MustBePresent="false"
/>
</xacml3:Apply>
<xacml3:AttributeValue
DataType="http://www.w3.org/2001/XMLSchema#string">value</xacml3:AttributeValue>
</xacml3:Apply>
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-equal">
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-one-and-only" >
<xacml3:AttributeDesignator
AttributeId="A5"
DataType="http://www.w3.org/2001/XMLSchema#string"
Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource"
MustBePresent="false"
/>
</xacml3:Apply>
<xacml3:AttributeValue
DataType="http://www.w3.org/2001/XMLSchema#string">value</xacml3:AttributeValue>
</xacml3:Apply>
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-equal">
<xacml3:Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-one-and-only" >
<xacml3:AttributeDesignator
AttributeId="A6"
DataType="http://www.w3.org/2001/XMLSchema#string"
Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource"
MustBePresent="false"
/>
</xacml3:Apply>
<xacml3:AttributeValue
DataType="http://www.w3.org/2001/XMLSchema#string">value</xacml3:AttributeValue>
</xacml3:Apply>
</xacml3:Apply>
</xacml3:Apply>
</xacml3:Apply>
</xacml3:Condition>
</xacml3:Rule>
</xacml3:Policy>
--- 编辑---
表达否定条件，例如不是(性别==男性)，你有两个选择:
To express negative conditions e.g. not(gender==male), you have two options:
- 可能值的集合是有限的，例如真/假、男/女、热/暖/冷，您乐于为每个案例制定政策或规则.
- 或者可能值的集合太长或无限，例如数值或公民身份列表(其中 180 多个).
在前一种情况下，您可以编写以下内容:
In the former case you can write the following:
policy checkGender{
apply firstApplicable
rule male{
target clause gender=="male"
permit
}
rule female{
target clause gender=="female"
permit
}
/**
* Optionally add a catch all case
*/
rule other{
target clause ... // Here you'd have to define other checks you are interested in
}
}
在后一种情况下，您需要编写否定条件.为此，您需要使用 XACML 条件.由于 XACML 条件仅存在于规则内，因此您需要深入到 XACML 规则级别.
In the latter case, you need to write a negative condition. To do that you need to use a XACML condition. Since XACML conditions only live inside rules, you need to go down to the XACML Rule level.
policy checkGender{
apply firstApplicable
rule notMale{
condition not(gender=="male")
permit
}
}
这篇关于使用 XACML 来表达策略，这是一个逻辑表达式的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
