<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:11pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;" dir="ltr">
<p>If at all possible, I'd strongly suggest to the vendor that what they're doing is horribly backwards.</p>
<p><br>
</p>
<p>That said, in situations such as these if I have no other choice, my approach has been to create a separate AttributeDefinition entry (with an id like "uid_SillyVendorNameHere") from the same source attribute, with whatever non-standard tweaks they vehemently
insist upon, and release that to them instead.</p>
<p><br>
</p>
<p>You absolutely won't want to change your working definition.<br>
</p>
<p><br>
</p>
<p>Michael<br>
</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> users <users-bounces@shibboleth.net> on behalf of XiaoXia Dong <x-dong@northwestern.edu><br>
<b>Sent:</b> Thursday, February 23, 2017 1:09:59 PM<br>
<b>To:</b> Shib Users<br>
<b>Cc:</b> Phil Tracy<br>
<b>Subject:</b> change definition of uid name and friendlyname</font>
<div> </div>
</div>
<div>
<div class="WordSection1">
<p class="MsoNormal">Hello Shib Experts,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have a vendor which does not work with the out of box definition of uid,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Here is the original one:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> <resolver:AttributeDefinition xsi:type="ad:Simple" id="uid" sourceAttributeID="uid"><o:p></o:p></p>
<p class="MsoNormal"> <resolver:Dependency ref="myLDAP" /><o:p></o:p></p>
<p class="MsoNormal"> <resolver:AttributeEncoder xsi:type="enc:SAML1String" name="urn:mace:dir:attribute-def:uid" /><o:p></o:p></p>
<p class="MsoNormal"> <resolver:AttributeEncoder xsi:type="enc:SAML2String" name="urn:oid:0.9.2342.19200300.100.1.1" friendlyName="uid" /><o:p></o:p></p>
<p class="MsoNormal"> </resolver:AttributeDefinition><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In order to make this particular app work, I need to swap the name and friendlyName of uid,
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> <resolver:AttributeDefinition xsi:type="ad:Simple" id="uid" sourceAttributeID="uid"><o:p></o:p></p>
<p class="MsoNormal"> <resolver:Dependency ref="myLDAP" /><o:p></o:p></p>
<p class="MsoNormal"> <resolver:AttributeEncoder xsi:type="enc:SAML1String" name="urn:mace:dir:attribute-def:uid" /><o:p></o:p></p>
<p class="MsoNormal"> <resolver:AttributeEncoder xsi:type="enc:SAML2String" name="uid" friendlyName="urn:oid:0.9.2342.19200300.100.1.1" /><o:p></o:p></p>
<p class="MsoNormal"> </resolver:AttributeDefinition><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I realized that this is a global change and it could potentially break some other applications. I like to get opinions from shib experts how risky this change is and whether it is a safe change from SAML2.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you.<o:p></o:p></p>
</div>
</div>
</body>
</html>