how to reference an existing attribute in resolver.xml

[Cantor, Scott]

On 6/27/13 7:59 PM, "David Bantz" <dabantz at alaska.edu> wrote:
>
>Seems it would be nice to be able to release the same attribute values
>under different names.  We have one service that insisted on "LastName"
>rather than surname, for example.  We did just duplicate that resolver
>definition with a different ID.

You don't have to duplicate, just create a new one that depends on an
older one as the source attribute, and it will duplicate the values into a
new attribute with different encoders.

>  But we have other attributes that entail comparing and computing values
>in a script and it seems wasted overhead to do that more than once for
>each login.  Am I missing a simple way to indicate this attribute is just
>a quirky name for this already resolved attribute and release it with the
>quirky name to the SP that requires it?

See above.

Making one definition expressible with different names would break the
whole release policy / resolver relationship. Though one idea that comes
to mind is implementing a "Scripted" Attribute Encoder, that literally
generates any XML on the wire that it wants with access to the usual
request context. Weird, but probably doable.

-- Scott