<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:12pt"><div><span>I do indeed care strongly. I would prefer to not have to update my config for every PF customer that comes along.</span></div><div><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> "Cantor, Scott" <cantor.2@osu.edu><br> <b><span style="font-weight: bold;">To:</span></b> Shib Users <users@shibboleth.net> <br> <b><span style="font-weight: bold;">Sent:</span></b> Monday, February 18, 2013 1:40 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> RE: SP Signed SAML requests<br> </font> </div> <br>
> OK, rule added and issue resolved (for two different PingFederate IDps). For<br>> what it's worth, anyone connecting to Ping Identity's Ping Federate IDp will<br>> have to have request signing turned on to work with that system. According<br>> to my customer, they cannot turn that off on their side.<br><br>They are, not surprisingly, incorrect. If you care strongly, I can put them in touch with somebody who can tell them how.<br><br>-- Scott<br><br><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>