<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
On Aug 13, 2014, at 6:48 PM, Farzan Qureshi <<a href="mailto:fqureshi@rosmini.school.nz">fqureshi@rosmini.school.nz</a>> wrote:<br>
<div><br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr" style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<strong>Error Message: No peer endpoint available to which to send SAML response</strong><br>
</div>
<br class="Apple-interchange-newline">
</blockquote>
</div>
<div><br>
</div>
<div>This means the ACS URL in your AuthnRequest does not match any ACS URL in the metadata given to the IdP. ACS URL's are an EXACT match, case included, etc. Your SP is sending something that is wrong, or you gave the IdP the wrong metadata. Either way, it
doesn't match.</div>
<div><br>
</div>
<div>Get a copy of FireFox and install the SAML Tracer plugin. Open SAML Tracer and run your test. You will see the exact value in the AuthnRequest the SP is sending. Match it against the metadata provided to the IdP. Then trace back to figure out why they
are different.</div>
<div><br>
</div>
<div>Paul</div>
<br>
<div apple-content-edited="true">Paul Hethmon<br>
Chief Software Architect<br>
<a href="mailto:paul.hethmon@clareitysecurity.com">paul.hethmon@clareitysecurity.com</a><br>
<br>
</div>
<br>
</body>
</html>