<div dir="ltr">Under v2 I used to be able to attach multiple AttributeEncoders to a particular attribute & release all of the encoded permutations of the attribute with a basic:ANY filter.  In v3 it doesn't seem to be doing that.  Rather it seems to release only the final encoded attribute.  Is this intentional?<div><br></div><div>Example:</div><div><br></div><div><div> <resolver:AttributeDefinition id="ucStudentID" xsi:type="Simple" xmlns="urn:mace:shibboleth:2.0:resolver:ad"</div><div>                                  sourceAttributeID="ucStudentID"></div><div>        <resolver:Dependency ref="directory"/></div><div>                </div><div>        <resolver:AttributeEncoder xsi:type="SAML2String" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"</div><div>                                   name="urn:oid:1.3.6.1.4.1.30729.2.2.1.6.1" friendlyName="cs_cust_id"/></div><div><br></div><div>        <resolver:AttributeEncoder xsi:type="SAML1String" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"</div><div>                                   name="urn:mace:dir:attribute-def:ucStudentID"/></div><div>        </div><div>        <resolver:AttributeEncoder xsi:type="SAML2String" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"</div><div>                                   name="1.3.6.1.4.1.9902.2.1.1" friendlyName="ucStudentID"/></div><div>    </resolver:AttributeDefinition></div><div><br></div><div>only ucStudentID goes out, not cs_cust_id.  Did something change in the configuration between v2 and v3 that I need to setup in my filter to say I want all the encodings for SAML2 to go out?</div><div><br></div><div>Thanks</div><div><br>Dave</div><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>David Langenberg<div>Identity & Access Management Architect</div><div>The University of Chicago</div></div></div></div>
</div></div>