"SAML message intended destination endpoint URI required by binding was empty"

[Cantor, Scott]

On 6/5/13 4:23 PM, "Liam Hoekenga" <liamr at umich.edu> wrote:
>
>I'm trying to configure WSO2's "Carbon" server to use our Shib IdP for
>authentication.

Good luck. (Not being sarcastic, just assuming.)

>15:25:02.897 - WARN
>[edu.internet2.middleware.shibboleth.idp.profile.saml2.SSOProfileHandler:3
>44] - Error decoding authentication request message
>org.opensaml.ws.message.decoder.MessageDecodingException: No SAMLRequest
>or SAMLResponse query path parameter,
> invalid SAML 2 HTTP Redirect message

That one seems distinct, and is self-explanatory (the URL was just not
even carrying a message).

>Stupid question.  I'm getting that because the AuthnRequest looks like..
>
><saml2p:AuthnRequest xmlns:saml2p="urn:oasis:names:tc:SAML:2.0:protocol"
>ID="hcalffjcdahooaakphckclfaalgmlebdhofoepja"
>IssueInstant="2013-06-05T20:13:06.563Z" Version="2.0">

Yes, that's invalid per the rules for the binding.

>Is the top level AuthnRequest element the only place that the destination
>would show up?

Yes.

>It looks like I'm having an issue decoding the message... am I having
>problems finding the destination because I can't decode the message?

I don't think they're the same case, but maybe it's falling through
something in the code.

-- Scott