NameFormat Case Sensitivity

[Patrick Le]

We have a vendor app that we're having a little trouble federating. The vendor is claiming that it's the nameFormat of the email attribute we're sending over.

What we've configured in resolver.xml
        <resolver:AttributeEncoder xsi:type="enc:SAML2String" name="Email" nameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic" />

What we're sending:
         <saml2:Attribute Name="Email" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
            <saml2:AttributeValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">myemail at school.edu</saml2:AttributeValue>
         </saml2:Attribute>

What the vendor requires

         <saml2:Attribute Name="Email" nameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
            <saml2:AttributeValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">myemail at school.edu</saml2:AttributeValue>
         </saml2:Attribute>

The only difference is the "n" in nameFormat is lowercase but we're sending all of our attributes as NameFormat. Haven't been able to find anywhere to modify this on the IDP. Most searches discuss how to modify the attribute values themselves. Looking for a way to modify the actual word "NameFormat"

Thanks



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170404/905f544a/attachment-0001.html>