Mapped Attribute Value Always Passing Default

[Greg Haverkamp]

On Mon, Oct 31, 2016 at 12:28 PM, Losen, Stephen C. (scl) <
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/d769ec99/attachment.html>