<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I know I could define an ad hoc single-valued attribute in the resolver. </div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I’ve done something similar a few times already. But I understand the service to</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">require mail with the mail OID - not some ginned up ad hoc attribute.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">So apparently it seems I need to somehow jigger the attribute release </div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">policy to only allow (an arbitrary) one of the set of values if that is possible. </div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div> <div id="bloop_sign_1383587615529017088"><span style="font-family:helvetica,arial;font-size:13px"></span>-- <br>David Bantz<br><br></div> <br><p style="color:#A0A0A8;">On Monday, 4 November 2013 at 08:44:11, Cantor, Scott (<a href="mailto://cantor.2@osu.edu">cantor.2@osu.edu</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div>On 11/4/13, 12:36 PM, "David Bantz" <dabantz@alaska.edu> wrote:
<br>
<br>>Does anyone have a ready solution to releasing just one of the values of
<br>>a multi-valued attribute to an R&S service that requires the mail
<br>>attribute but breaks if sent multiple values of this multi-valued
<br>>attribute?
<br>
<br>I don't think there's any clean way unless you could base it on the value
<br>in some way.
<br>
<br>You could also create a second attribute definition for a single-valued
<br>version and use the same encoders, and just release it to that SP.
<br>
<br>-- Scott
<br>
<br>
<br>--
<br>To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net
<br></div></div></span></blockquote></body></html>