NativeSP 2.5.5 Attribute Transforming

[O'Dowd, Josh]

Thanks Scott,

I have simplified my config a little bit, by pulling the <AttributeResolver> element out into the <AttributeDefaults> just to see if I could get it to work.  I tried both with no dest, and a dest="differentName".  Neither worked.

Am I correct in assuming this resolver runs after attribute extraction and not before, and therefore should not need to map the transform-created attribute?  In other words, I should just see the new "differentName" in the request header with the new value, right?

Hmmm.  

-Josh

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Friday, October 23, 2015 2:22 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: NativeSP 2.5.5 Attribute Transforming

On 10/23/15, 4:04 PM, "users on behalf of O'Dowd, Josh" <users-bounces at shibboleth.net on behalf of Josh.O'Dowd at mso.umt.edu> wrote:

>While I have confirmed the regex is grouping a proper 8 character match, the ‘uid’ attribute value is not being transformed and is arriving at the application with its original value.

I don't recall whether it has defined behavior to use the same source and dest, but the intended way to signal you want replacement is to omit dest from the matching rule.

What I would expect it might do is create an additional uid attribute with the new value and the header would contain both, but it may well just not work.

-- Scott

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