Custom nameid getting released in version 2 but not version 3

[Cantor, Scott]

On 8/5/16, 6:46 PM, "users on behalf of shibboleth655 at lewenberg.com" <users-bounces at shibboleth.net on behalf of shibboleth655 at lewenberg.com> wrote:
>
>    We are using Shibboleth 3.2.1 with nameid-formats using the legacy 
>    generators. We define an attribute "mailNameID" with a nameid encoder in 
>    attribute-resolver.xml that depends on another attribute (in this case 
>    "mail"). In attribute-filter.xml we explicitly release "mailNameID" but 
>    we do _not_ release the "mail" attribute.
>
>    When we do this, the "mailNameID" does not get released. If we 
>    explicitly release the "mail" attribute along with "mailNameID", then 
>    "mailNameID" _does_ get released.

That strikes me as physically impossible based on what I know of the code and the order of processing, so I have no explanation for that and would like to see an issue filed for no other reason than understanding how that could ever be possible.

I would not expect V3 to behave any differently from V2, filtering happens after in both cases.

-- Scott