ORConfiguration

Namespace: urn:mace:shibboleth:2.0:afp
Schema: http://shibboleth.net/schema/idp/shibboleth-afp.xsd

1 Overview
2 Reference
3 PolicyRule Semantics
- 3.1 Example
4 Matcher Semantics
- 4.1 Example

Overview

The OR type is one of a very few filter plugin types which can function as a PolicyRule or a Matcher. It takes its behavior from its location. If it is defined within a <PolicyRequirementRule> (either directly or as a child of other logical operations), then it acts as a PolicyRule, otherwise it acts as a Matcher.

Reference

At least one <Rule> element must be present (these are interpreted as either <PolicyRequirementRule> or <PermitValueRule>/<DenyValueRule> based on the context).

PolicyRule Semantics

When used as a PolicyRule, the result is the logical OR of the evaluation of the child rules.

Example

The example means that the rule is applied if:

The principal is jsmith or
The SP is named https://sp.example.org or
The SP is named https://sp2.example.org

<PolicyRequirementRule xsi:type="OR">
   <Rule xsi:type="Requester" value="https://sp.example.org" />
   <Rule xsi:type="Requester" value="https://sp2.example.org" />
   <Rule xsi:type="PrincipalName" value="jsmith" />
</PolicyRequirementRule>

Matcher Semantics

When used as a Matcher, the allow or deny set result is the union of all sets resulting from the child rules (that is, it is the set of items in the results of any of the child rules).

Example

The example reads "Release those values for the attribuite 'uid' which match either of the regular expressions (starting with jsmi or ending with th)."

<AttributeRule attributeID="uid">
  <PermitValueRule xsi:type="OR">
     <Rule xsi:type="ValueRegex" regex="^jsmit.*$" />
     <Rule xsi:type="ValueRegex" regex="^.*th$" />
  </PermitValueRule>
</AttributeRule>