<div dir="ltr">Thanks, your particularly hostile response--with supporting evidence--will give me the capital I need to convince management we need to fix this.<div><br></div><div>Chris</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Jun 24, 2014 at 9:38 AM, Peter Schober <span dir="ltr"><<a href="mailto:peter.schober@univie.ac.at" target="_blank">peter.schober@univie.ac.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
* Christopher Peters <<a href="mailto:cjpeters@uci.edu">cjpeters@uci.edu</a>> [2014-06-24 18:20]:<br>
<div class="">> 1) Is it wrong to have two encoders on an attribute? It serves the<br>
> purpose we had of matching the name no matter which scheme the SP chose.<br>
> And it didn't seem to me that URN:MACE or OID formats were specific to a<br>
</div>> particular protocol [...]<br>
<br>
It is (wrong) and they are (protocol specific): The use of legacy<br>
names is specifically ruled our for use within SAML2, cf. 3.2. of<br>
<a href="http://macedir.org/docs/internet2-mace-dir-saml-attributes-latest.pdf" target="_blank">http://macedir.org/docs/internet2-mace-dir-saml-attributes-latest.pdf</a><br>
<div class=""><br>
> 2) Is there an easy way--either on the IDP side or SP side--to filter down<br>
> to a single encoding?<br>
<br>
</div>Use the software's default configuration? That will release the SAML1<br>
naming convention for SAML1 protocol messages, and the SAML2 naming<br>
convention for SAML2 protocol messages.<br>
<div class=""><br>
> What would really make my life simpler is an improvement to the SP code<br>
> that took the attributes and when it saw "12345;12345" just returned<br>
> "12345". The classic array dupe reduction. But I'm not looking for an<br>
> improvement to Shibboleth to solve my issue. Maybe there's some way to<br>
> accomplish this already that I don't know?<br>
><br>
> In the end, if there's not a simple fix my larger scale resolution will be<br>
> to split the encodings into two separate attributes on the IDP side and<br>
> release the right ones at the right time, but that's confusing to<br>
> maintain.<br>
<br>
</div>"Do nothing" seems to work just fine for every other IDP deployment on<br>
the planet?<br>
-peter<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">
<font face="arial black, sans-serif">Chris Peters</font><br>Middleware Services Developer<br>Office of Information Technology - NSP<br>(949) 824-6845<br><a href="mailto:cjpeters@uci.edu" target="_blank">cjpeters@uci.edu</a><br>
</div>
</div>