Custom nameid getting released in version 2 but not version 3

[Cantor, Scott]

On 8/3/16 7:31 PM, Klingenstein, Nate wrote:
>> There are numerous things that don't work right in V2 when you create
>> esoteric filter policies that act on other attributes. In V3, they all do
>> predictable things, but those things aren't always what people expect them
>> to be.
> 
> A great illustrative example arose during the Installfests that led to
> this getting deprecated because of sheer confusion.  You can copy and
paste
> from the referenced issue, or fiddle with it.  It still doesn't make
any sense
> to me either.

That isn't what was happening though, at least not in the policy posted.
Applying an Allow rule using an attribute/value to trigger the policy
works fine. Using one *inside* a rule has different implications.

-- Scott