Transform SP Attribute Resolver: merging several into one value

[Peter Schober]

* Peter Schober <peter.schober at univie.ac.at> [2014-01-16 21:24]:
> * Cantor, Scott <cantor.2 at osu.edu> [2014-01-16 15:57]:
> > On 1/16/14, 8:48 AM, "Peter Schober" <peter.schober at univie.ac.at> wrote:
> > 
> > >Now, how would I go about doing it the other way round, creating
> > >displayName from "$sn $givenName"?
> > 
> > The Template plugin, typically. That's the example I use in the
> > docs.
> 
> Should have just scrolled down 10 lines.

The problem then shifts from IDPs who only send one (displayName) or
the other (givenName, sn) to those thoughtful IDPs that want to
support both kinds of SPs -- those who can only process one form or
the other -- and will send both versions, causing the Template to
create multiple values for displayName (which somewhat ironically only
differs from 'cn' in being single-valued in its upstream definition).

But I guess I could block one (givenName, sn) based on the presence of
the other (displayName) in the attribute-policy.xml, avoiding that
problem and still being able get a name populated no matter what the
IDPs send.
-peter