Mapped Attribute Value Always Passing Default

[Losen, Stephen C. (scl)]

Hi folks,

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.  

Stephen C. Losen
ITS - Systems and Storage
University of Virginia
scl at virginia.edu    434-924-0640

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Monday, October 31, 2016 1:25 PM
To: Shib Users
Subject: RE: Mapped Attribute Value Always Passing Default

> When it comes to the documentation, should it be updated to reflect that
> the default is always passed?

It isn't.

> Or if that's not how it's supposed to work
> maybe a bug report filed for that plugin? From what I can tell the
> original configuration I had should have worked.

It's not a bug, it's a "this is a very complex plugin that people don't really understand the behavior of". Somebody who does understand it can tell you why your approach was off, but that somebody isn't me.

-- Scott

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net