<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>Adding to Scott's answer…</div>
<div><br>
<blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="font-family: Calibri, sans-serif; font-size: 15px; ">These
Friendly names are eduPersonScopeAffiliation, eduPersonTargetID, etc… but there are also institution-specific attributes like ‘xyzUserID’ or xyzHousingLocation or the like…</span>
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
</div>
</span></blockquote>
<div><br>
</div>
<div>Friendly names are not intended to be unique or used for any purpose beyond human readability.</div>
<div><br>
</div>
<div>You should emphasize standardization of SAML attribute names whenever possible. You're going to end up with something complicated somewhere if you don't.</div>
<div><br>
</div>
<div>The simplest and cleanest, other than standardization, would probably be to map multiple SAML attribute names to a single attribute name for consumption by your application using the SP and attribute-map.xml.</div>
<div><br>
</div>
<div><a href="https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPAddAttribute">https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPAddAttribute</a></div>
</div>
</div>
</body>
</html>