ECMA to access SubjectCanonicalizationContext in Resolver

[Cantor, Scott]

On 11/10/15, 10:21 PM, "dev on behalf of Michael A Grady" <dev-bounces at shibboleth.net on behalf of mgrady at unicon.net> wrote:



>The one remaining question would be "is there any simple activation condition I could use to get this special Data Connector (DC) and this attribute definition to only run at c14n time"? I.e. so the normal resolution step doesn't try to run it? Because I needed to account for that in the script, in order to ensure that there was at least one "empty" value for the attribute, so the associated DC didn't error out when it tried to resolve rawUsername.get(0). Maybe there is a better way to handle the latter?

A data connector shouldn't need to error out, you can tell them to treat no results as a normal conditon. But that should be the default. How is it erroring out?

There's nothing explicit as a condition, other than an actual check for, I guess, one of the contexts, but it's always going to be situational. I believe the processes that run after c14n clean up the tree and remove that context, so I don't think there would be a c14n context child in the normal case. You're basically moving error handling/checking around, so I'm not sure that's any better particularly given that it would have to be a bean reference to a condition.

-- Scott