AttributeDefinition: Merge results from 2 Data Connectors

[Joel Levin]

Thank you Gary and Scott!

Yes -- I had misunderstood.

It works.


<AttributeDefinition xsi:type="Template" id="displayName">
            <Dependency ref="givenName" />
            <Dependency ref="sn" />
        <AttributeEncoder xsi:type="SAML2String"
name="urn:oid:2.16.840.1.113730.3.1.241" friendlyName="Display Name" />
        <Template>
            <![CDATA[
                ${givenName} ${sn}
            ]]>
        </Template>
            <SourceAttribute>sn</SourceAttribute>
            <SourceAttribute>givenName</SourceAttribute>
        </AttributeDefinition>




On Wed, Feb 8, 2017 at 3:21 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 2/8/17, 6:07 PM, "users on behalf of Joel Levin" <
> users-bounces at shibboleth.net on behalf of joel.aaron.levin at gmail.com>
> wrote:
>
> >    Getting closer -- leveraging the Dependency as the givenName and
> lastName come from 2 distinct AttributeResolvers
> > (each has their own AttributeDefinitions).
>
> Gary gave you the exact example we were trying to tell you to use. You
> don't need a script, use Template.
>
> -- Scott
>
>
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170208/7e6ff3e9/attachment.html>