Need help with canonicalization and attribute resolver in a mutual auth scenario.

[Peter Schober]

* Johan Åkerstrøm <Johan.Akerstrom at skill.no> [2015-07-14 23:40]:
> This is currently all that I have in my attribute-resolver.xml
> 
>    <resolver:AttributeDefinition id="affiliation" xsi:type="ad:Simple" sourceAttributeID="affiliation">
>         <resolver:Dependency ref="staticAttributes" />
>     </resolver:AttributeDefinition>

Not sure how that's related to the current thread but if you undo the
removal of the (commented-out) default AttributeDefinition for
affiliation you'll find that there needs to be an AttributeEncoder
attached to the attribute definition, describing the formal
on-the-wire representation (nameformat, name, friendlyname) of that
attribute.
So the above definition will not generate anything that makes into the
SAML assertion as attribute.

> Shouldn't this give me an attribute with the name affiliation and the value member in my SAML assertion? 
> Feels like I am missing something fundamental here. 

Probably just the AttributeEncoder child element -- and maybe adapting
your attribute-filter.xml. By default the IDP releases no attributes,
that's your decision.
-peter