Issue with releasing eduPersonPrincipalName to Specific SP
cbernard
cbernard at uoregon.edu
Wed Apr 26 14:29:55 EDT 2017
Hi Edward,
I ran into something similar, an SP could see other attributes, but not the
eduPersonTargetedID I was passing. To resolve the issue, I added a line
similar to the third line below within my attribute-resolver so that the SP
received the NameID element:
<resolver:AttributeEncoder xsi:type="enc:SAML1ScopedString"
name="urn:mace:dir:attribute-def:eduPersonPrincipalName" encodeType="false"
/>
<resolver:AttributeEncoder xsi:type="enc:SAML2ScopedString"
name="urn:oid:1.3.6.1.4.1.5923.1.1.1.6"
friendlyName="eduPersonPrincipalName" encodeType="false" />
<resolver:AttributeEncoder xsi:type="enc:SAML2ScopedStringNameID"
xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
nameFormat="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent" />
Regards,
Chris
--
View this message in context: http://shibboleth.1660669.n2.nabble.com/Issue-with-releasing-eduPersonPrincipalName-to-Specific-SP-tp7632835p7632836.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.
More information about the users
mailing list