<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 6/23/15 8:45 PM, IAM David Bantz
wrote:<br>
</div>
<blockquote
cite="mid:CAJ9XvwE3suKxcmSMKnUYKq+G3HMnnWc9r3xY7L89FCJE8oFfFA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div>
<p class=""><span class="">12:37:43.141 - WARN
[edu.internet2.middleware.shibboleth.idp.profile.saml2.SSOProfileHandler:400]
- <br>
Error decoding authentication
request message </span>org.opensaml.ws.message.decoder.MessageDecodingException:
<br>
No SAMLRequest or SAMLResponse query
path parameter, invalid SAML 2 HTTP Redirect message</p>
</div>
</div>
</blockquote>
<br>
<br>
I don't think this has anything to do with the other stuff you
mentioned. They are simply not sending a valid SAML 2 Redirect
binding request. Most likely they are doing the POST binding, but
mistakenly sending it to the IdP's Redirect endpoint. Just change
the binding or the endpoint in use.<br>
<br>
If that's not it, then the message means what it says: there's
literally not a query parameter called in SAMLRequest in the HTTP
request to the IdP. You should be able to see exactly what they are
sending in your browser, possibly using Firefox Live Headers or SAML
Tracer.<br>
<br>
All the other stuff you mentioned re: the MCB, authN contexts, etc,
is not related to the above error.<br>
<br>
</body>
</html>