<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:12pt"><div><span>OK, rule added and issue resolved (for two different PingFederate IDps). For what it's worth, anyone connecting to Ping Identity's Ping Federate IDp will have to have request signing turned on to work with that system. According to my customer, they cannot turn that off on their side.</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:12 PM<br>
<b><span style="font-weight: bold;">Subject:</span></b> RE: SP Signed SAML requests<br> </font> </div> <br>
> Having turned off signing, I have a customer now that reports this error:<br>> <br>> <br>> Error from identity provider:<br>> Status: urn:oasis:names:tc:SAML:2.0:status:Requester<br>> Message: Signature required<br>> <br>> Will I need to set a rule like this for them?<br><br>Yeah, more or less.<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>