unscoped affiliation not passing...

Mike Flynn shibbolethlynda at yahoo.com
Mon Sep 9 10:52:53 EDT 2013


I get this attribute from lots of Idps and it works fine.  I just hooked up another Idp that wants to pass unscoped affiliation.  This is what is in the assertion:

<saml2:AttributeStatement> <saml2:Attribute Name="urn:oid:1.3.6.1.4.1.5923.1.1.1.1" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri" > <saml2:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string" >Department</saml2:AttributeValue> </saml2:Attribute> </saml2:AttributeStatement>

Here is mail from the same assertion and it passes just fine:
<saml2:AttributeStatement> <saml2:Attribute FriendlyName="mail" Name="urn:oid:0.9.2342.19200300.100.1.3" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri" > <saml2:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string" >someuser at someschool.com</saml2:AttributeValue> </saml2:Attribute> </saml2:AttributeStatement>
URN and nameFormat are correct - Data looks fine...  The only difference I can see is friendlyName is missing. But that should not make a difference, should it?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130909/4e5fffc6/attachment.html 


More information about the users mailing list