ECMA to access SubjectCanonicalizationContext in Resolver

[Cantor, Scott]

On 11/11/15, 5:19 AM, "dev on behalf of Rod Widdowson" <dev-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:



>> Rod might have a view on whether it's possible to adjust the behavior of
>> scripted attributes or connectors to not return anything with an empty
>value set
>> (as distinct from empty values).
>
>Would there not be backward compatibility issues?  Or do you mean a "no
>attribute if no values" setting.  Not sure I like that for the attribute
>resolver ("why do I not get an attribute if I run this scripted attribute",
>but it makes sense for the dataconnector.

I was thinking that, but then I also started wondering if there's an actual regression here vs V2. Since I don't see this kind of error on V2 in my config, I wondered if V2 was injecting attributes with no values into the scripting context of the LDAP filter template.

Either way, that would also be a solution, just not injecting them. That eliminates the variable creating the array exception.

Regardless, we need to trap the runtime errors, so that's just a bug.

-- Scott