NativeSP 2.5.5 Attribute Transforming

[Cantor, Scott]

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

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

If you mean ApplicationDefaults, any resolvers defined in an override will completely replace anything at the default level.

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

It runs after extraction, yes.

>  In other words, I should just see the new "differentName" in the request header with the new value, right?

Yes, but that's not extraction, that's an export to the headers on every request from whatever is in the session. Extraction is just the initial pull from the assertion to populate the session. It probably should have just been merged into the resolver stage, but it's historical at this point.

There is no way, FWIW, to really verify what a regex is doing unless you run the same code. That would require building a test program on top of xerces-c to exercise the regex support it exposes that I'm reusing.

You could turn up the logging and see if it shows anything.

-- Scott