The Shibboleth IdP V3 software has reached its End of Life and is no longer supported. This documentation is available for historical purposes only. See the IDP4 wiki space for current documentation on the supported version.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Overview

Each <afp:AttributeRule> defines a filter operation to be applied to the values one specified attribute.

Each rule is either a permit rule in which case the filtered values are added to the permit list as described here or a deny rule in which case the filtered attributes are added to the deny list as described.

Examples

<afp:AttributeRule attributeID="eduPersonPrincipalName">
    <afp:PermitValueRule xsi:type="basic:AttributeValueString" value="jsmith" ignoreCase="true" />
</afp:AttributeRule>

Reference

Schema Name

Elements and types described in this page and its children are defined in one of three schema

Attributes

NameTypeDescription
attributeIDStringThis required attributes specifies the attribute name (as defined by an AttributeDefinition statement in the attribute-resolver.xml file
permitAnyboolean

If this is present and is "true", then there no child elements should be provided and the entire statement is shorthand for

<afp:AttributeRule attributeID="...">
   <afp:PermitValueRule xsi:type="basic:ANY" />
</afp:AttributeRule>

Child Elements

One of the either <afp:DenyValueRule> or <afp:PermitValueRule>  is specified as a child element.  These elements must have a type specified by the xsi:type being one of the Common Types.

This rule should be of a matcher type.  If it is of PolicyRule type then it will be converted as described here.

  • No labels