<div dir="ltr">Hi,<br><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="im">
</div>Yeah, that's broken then. They picked the SAML 1 / Shib request endpoint<br>
for the SAML 2 binding. Their bug.<span class=""><font color="#888888"><br></font></span></blockquote><div> <br></div><div>Thank you for your help. That was in fact the issue and I got the vendor to acknowledge that! I appreciate your help not just for helping solve this, but because I feel like I have a slightly better understanding.<br>
<br></div><div>Unfortunately I'm now on to this vendor's next problem, of course. My logs tells me that "SAML message intended destination endpoint URI required by binding was empty" which seems pretty straight forward, but in a previous message from the SP vendor they linked me to <a href="http://en.wikipedia.org/wiki/SAML_2.0#Authentication_Request_Protocol">a wikipedia section on the SAML2 auth request protocol</a>, which now looking at it, doesn't have a destination attribute. Am I reading this wrong?<br>
<br>Thanks,<br>Ian<br><br><br></div></div></div></div>