<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:12pt"><div><span><font size="3">Well, I asked them a while back if they were willing to change it and send a single value but they were not. I do not have much leverage since these are customers and are paying us for our service. We try to be as </font>accommodating<font size="3"> as possible since that is where our bread is buttered....</font></span></div><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt;"><br></div> <div style="font-family: arial, helvetica, sans-serif; font-size: 12pt;"> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Peter Schober <peter.schober@univie.ac.at><br> <b><span style="font-weight: bold;">To:</span></b>
users@shibboleth.net <br> <b><span style="font-weight: bold;">Sent:</span></b> Thursday, December 6, 2012 7:16 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: Handling a multi-value attribute question<br> </font> </div> <br>
* Michael A Grady <<a ymailto="mailto:mgrady@unicon.net" href="mailto:mgrady@unicon.net">mgrady@unicon.net</a>> [2012-12-06 16:08]:<br>> At Illinois (my institutional home for many years) givenName was a<br>> multi-valued attribute (certainly defined as such in the standard<br>> schema), but we also maintained a local attribute that was the<br>> singly valued "official first name". And, in the context of all of<br>> our attribute release for federated partners, we'd encode/release<br>> that local attribute as the value for the standard givenName field<br>> -- since no partners actually wanted the multi-valued field. Not<br>> sure why this particular school would insist on releasing the<br>> multi-valued form unless they don't have an easy source of a<br>> singly-valued field, but that is, of course, up to them.<br><br>I completely missed that of those 140 institutions only a single one<br>is causing this issue. Talking
to them then becomes the most obvious<br>choice, I'd say.<br>My comments were under the assumption that a large percentage of those<br>140 institutions were doing this.<br><br>I also fully agree with Michael (and Scott) that givenName & sn are<br>just fine as they are and if the institution doesn't like the choice<br>you've made (first/last/random value) than they should be limiting the<br>SAML attributes to a single value, no matter what's in their local<br>systems,<br>-peter<br>--<br>To unsubscribe from this list send an email to <a ymailto="mailto:users-unsubscribe@shibboleth.net" href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br><br><br> </div> </div> </div></body></html>