how to reference an existing attribute in resolver.xml

[David Bantz]

I did the experiment and, for the record, confirmed Scott's answer (I know, a little like confirming the Pope is Catholic).

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.  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?

David Bantz

On Thu, 27 Jun 2013, at 12:02 , "Cantor, Scott" <cantor.2 at osu.edu> wrote:

> 
> 
> On 6/27/13 3:15 PM, "Nate Klingenstein" <ndk at internet2.edu> wrote:
> 
>> That would make it impossible to select one encoding versus another
>> encoding by SP by using the attribute filter engine.  With two encoders
>> for one protocol, I dunno what would happen -- whether you'd get both
>> encodings(and two copies of the attribute) in every assertion, or whether
>> one would take precedence, or what.
> 
> You should get both. May or may not matter, but adds some overhead.
> 
> -- Scott
> 
> 
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net