<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:12pt"><div><span>Understood. Thanks, Scott.</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"> <hr size="1"> <font size="2" face="Arial"> <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, August 12, 2013 8:16 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: Yet another Idp error after SP upgrade<br> </font> </div> <div class="y_msg_container"><br>On 8/12/13 10:55 AM, "Mike Flynn" <<a ymailto="mailto:shibbolethlynda@yahoo.com"
href="mailto:shibbolethlynda@yahoo.com">shibbolethlynda@yahoo.com</a>> wrote:<br><br>>No keys have changed at this point. All metadata files, .cer/.pem files<br>>were brought over from the old servers in their entirety and now<br>>including the original working config file.<br><br>If the key didn't change, then the entityID did. Nothing else can cause<br>that error (assuming it was working before).<br><br>What you do now has no impact on the metadata they have. And that metadata<br>is wrong for the configuration you now have, which means either the<br>metadata changed or your entityID and/or key did. That is not in dispute<br>here, it's just a fact.<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> </div></body></html>