filter warning: Ignoring targeted attribute [...] applying to actual attribute

[Paul B. Henson]

> From: Cantor, Scott
> Sent: Wednesday, December 03, 2014 12:46 PM
>
> Yes, which means you have an AttributeRule against eduPersonEntitlement
> and inside that there's some kind of permit/deny rule with an attributeId
> set. That doesn't work, and it never did, so the warning was added to
> highlight that. In this case, it's superfluous, in a different case, it's
> potentially not working the way somebody thought it did.

Ah, ok; I see; so you can use (for example) an AttributeValueString within either a PolicyRequirementRule or an AttributeRule section, and in the former you need to explicitly specify an attributeID value to look at, whereas in the latter it implicitly operates upon the attributeID specified in the enclosing AttributeRule.

Fortunately, in my configuration, it is the same attribute specified for both the AttributeRule and the AttributeValueString within, so semantically it was doing the right thing, just with extraneous parameters.

Just to confirm, for a block such as:

<afp:AttributeRule attributeID="eduPersonEntitlement">
    <afp:PermitValueRule xsi:type="basic:AttributeValueString" attributeID="eduPersonEntitlement"
                                value="foobar" />
</afp:AttributeRule>

it should be simply:

<afp:AttributeRule attributeID="eduPersonEntitlement">
    <afp:PermitValueRule xsi:type="basic:AttributeValueString" value="foobar" />
</afp:AttributeRule>

Cool, thanks for the clarification. It was just a little confusing for the warning to say ignoring X, using X instead, when they were the exact same thing :).