Encoding attributes with multiple encoders

David Langenberg davel at uchicago.edu
Sun Aug 9 10:38:10 EDT 2015


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?

Example:

 <resolver:AttributeDefinition id="ucStudentID" xsi:type="Simple"
xmlns="urn:mace:shibboleth:2.0:resolver:ad"
                                  sourceAttributeID="ucStudentID">
        <resolver:Dependency ref="directory"/>

        <resolver:AttributeEncoder xsi:type="SAML2String"
xmlns="urn:mace:shibboleth:2.0:attribute:encoder"

 name="urn:oid:1.3.6.1.4.1.30729.2.2.1.6.1" friendlyName="cs_cust_id"/>

        <resolver:AttributeEncoder xsi:type="SAML1String"
xmlns="urn:mace:shibboleth:2.0:attribute:encoder"

 name="urn:mace:dir:attribute-def:ucStudentID"/>

        <resolver:AttributeEncoder xsi:type="SAML2String"
xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
                                   name="1.3.6.1.4.1.9902.2.1.1"
friendlyName="ucStudentID"/>
    </resolver:AttributeDefinition>

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?

Thanks

Dave

-- 
David Langenberg
Identity & Access Management Architect
The University of Chicago
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150809/0e7fd85b/attachment.html>


More information about the users mailing list