IdPFilterRequirementScript always returns true

[Cantor, Scott]

On 2/28/12 12:55 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>
>I see that attributeId and attributeValue are indeed set to null by
>intention when it is invoked as a PolicyRequirementRule.  They only take
>take values when they are used as an AttributeRule.  I'm not super
>familiar with the filtering engine internals, but I guess that makes
>sense, since when it's the former there's probably not a specific
>attribute or value being evaluated at that point.  It's used to
>determine whether the subordinate attribute rules should fire.

That's correct.

>Yeah, not sure about that probably some other subtle syntactic error you
>introduced. I don't think that the script should error out because the
>conditionals are taken out.  They are completely unrelated to whatever
>you are doing by accessing things from the filter context.

It's just erroring out because the code is calling methods on null
objects. Removing the null check just lets it drop into non-working code.

-- Scott