Mapped Attribute Value Always Passing Default

[Brandon McKean]

That would explain it then. My interpretation of its description was
that it looked at multi-value attributes as a single entity, rather than
piecemeal.

Thanks to everyone for clarifying this.

-- 
Brandon McKean
IT / Systems
Linux Administrator
(540)568-4235

On 10/31/2016 03:43 PM, Greg Haverkamp wrote:
>
> On Mon, Oct 31, 2016 at 12:28 PM, Losen, Stephen C. (scl)
> <scl at eservices.virginia.edu <mailto:scl at eservices.virginia.edu>> wrote:
>
>     Is the source attribute multi-valued?  I think the mapped plugin
>     generates an output value for each input value, so if you have one
>     input value that matches, and one that does not, then you get two
>     output values, one of which is the default.
>
>
> It will absolutely do this.  ("The content is matched against each
> input value and if it matches, then the <ReturnValue> is output.")
>  Had me stumped for a while, when I tried using it shortly after my v3
> upgrade.  (More than just ignoring Scott's recommendation to upgrade
> in-place, I not only did a "clean" upgrade, I also changed some
> functionality, ditching my JDBC-resolved attributes and trying to use
>  Mapped attributes for the first time.  Only a small segment of my
> population at the time produced multiple values...)
>
> Greg
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161031/b877ceff/attachment.html>