<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<font face="Helvetica, Arial, sans-serif">1) In our
attribute-resolver.xml file is the following definition:<br>
<br>
<font face="monospace"><AttributeDefinition
xsi:type="SAML2NameID" id="<b>eduPersonTargetedID</b>"
nameIdFormat="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"><br>
<InputDataConnector ref="ComputedIDConnector"
attributeNames="ComputedID"/> <br>
<AttributeEncoder xsi:type="SAML2XMLObject"
name="urn:oid:1.3.6.1.4.1.5923.1.1.1.10" friendlyName="<b>eduPersonTargetedID</b>"
/><br>
</AttributeDefinition></font><br>
<br>
2) In the default attribute release payload in our
attribute-filter.xml file is the following:<br>
<br>
<font face="monospace"><AttributeRule attributeID="<b>eduPersonTargetedID</b>"><PermitValueRule
xsi:type="ANY" /></AttributeRule></font><br>
<br>
3) Using the Firefox SAML tracer, I see in the
saml2:AttributeStatement the following:<br>
<br>
<font face="monospace"><saml2:AttributeStatement><br>
<br>
<saml2:Attribute FriendlyName="<b>eduPersonTargetedID</b>"<br>
Name="urn:oid:1.3.6.1.4.1.5923.1.1.1.10"<br>
NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri"<br>
><br>
<saml2:AttributeValue><br>
<saml2:NameID
Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"<br>
NameQualifier="urn:mace:incommon:jmu.edu"<br>
SPNameQualifier=<a class="moz-txt-link-rfc2396E" href="https://demo.jmu.edu/sso/">"https://demo.jmu.edu/sso/"</a><br>
>Tilw+llggW2JJUhjwrSWO/RBkyk=</saml2:NameID><br>
</saml2:AttributeValue><br>
</saml2:Attribute></saml2:AttributeStatement></font><br>
<br>
3) Using the aacli command, I see in the saml2:AttributeStatement
the following:<br>
<br>
<font face="monospace"> <saml2:AttributeStatement><br>
<br>
<saml2:Attribute FriendlyName="<b>eduPersonTargetedID</b>"
Name="urn:oid:1.3.6.1.4.1.5923.1.1.1.10"
NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri"><br>
<saml2:AttributeValue><br>
<saml2:NameID
Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"
NameQualifier="urn:mace:incommon:jmu.edu"
SPNameQualifier=<a class="moz-txt-link-rfc2396E" href="https://demo.jmu.edu/sso/">"https://demo.jmu.edu/sso/"</a>>Tilw+llggW2JJUhjwrSWO/RBkyk=</saml2:NameID><br>
</saml2:AttributeValue><br>
</saml2:Attribute><br>
<br>
</saml2:AttributeStatement></font><br>
<br>
<br>
What's the advantage of configuring an attribute in the
attribute-resolver.xml file as a <b>SAML2NameID</b> type? <br>
<br>
When I use the aacli command on many of our InCommon Federation
member entityIDs that are getting our Default attribute payload,
the saml2:Subject NameID Format seems to mostly be transient
value.<br>
<br>
Right / wrong / indifferent, no reference is made to the
eduPersonTargetedID attribute in our saml-nameid.xml file or
relying-party.xml file.<br>
<br>
</font><font face="Helvetica, Arial, sans-serif"><font face="Helvetica, Arial, sans-serif">Just trying to get my head
around why my predecessors configured things the way they did.<br>
<br>
Thanks,<br>
Don<br>
<br>
<br>
</font></font><font face="Helvetica, Arial, sans-serif"><font face="Helvetica, Arial, sans-serif">
</font></font>
<pre class="moz-signature" cols="72">--
D o n a l d L o h r
I n f o r m a t i o n S y s t e m s
J a m e s M a d i s o n U n i v e r s i t y
5 4 0 . 5 6 8 . 3 7 3 0
</pre>
</body>
</html>