Scoped attributes available to other definitions?

[Baron Fujimoto]

On Mon, Jan 13, 2014 at 08:29:00PM +0000, Cantor, Scott wrote:
>On 1/13/14, 3:20 PM, "Baron Fujimoto" <baron at hawaii.edu> wrote:
>>
>>I assume it must be syntax then, though I'm kind of at a loss since
>>the encoder bits were cut-paste from other working definitions.  AFAIK,
>>the order is pretty basic: dependencies, definition, encoder(s)
>
>My guess is encoders come before the value map. Definitions of plugins
>tend to add their syntax to the end of the general syntax, and encoders
>are a general feature.

Yup, it works if I put the encoders before the ValueMap. Thanks for
clearing up this mystery. The solution wasn't obvious to me from the error
message. I also probably assumed from the documentation[*] that it was
implied that the encoders should come last because the order in which the
process is described is "Prepare Attributes" and then "Attribute Encoding"
(and the sub-pages, e.g. for the mapped attribute, don't include encoding
sections in the examples).

[*] <https://wiki.shibboleth.net/confluence/display/SHIB2/IdPAddAttribute>

-baron
-- 
Baron Fujimoto <baron at hawaii.edu> :: UH Information Technology Services
minutas cantorum, minutas balorum, minutas carboratum desendus pantorum