error related to destinatioin when using opensaml and grails

[Paul Hethmon]

This is really a user list question unless you're going to hack Shibboleth to allow that behavior. Shib requires a strict URL match for the ACS endpoints. If any application needs to send state information (your ID value), then that's what the relay state is for. The grails application needs to change.

Paul


From: Mitu Singh <mitusingh27 at yahoo.com<mailto:mitusingh27 at yahoo.com>>
Reply-To: Shibboleth Dev <dev at shibboleth.net<mailto:dev at shibboleth.net>>
Date: Monday, August 26, 2013 4:41 PM
To: Shibboleth Dev <dev at shibboleth.net<mailto:dev at shibboleth.net>>
Subject: error related to destinatioin when using opensaml and grails

decoding.BaseSAMLMessageDecoder
SAML message intended destination endpoint 'http://localhost:8080/myIdp/SPInitRedirect/receiveSSORequest/940iuuikfpkqru5l' did not match the recipient endpoint 'http://localhost:8080/myIdp/grails/SPInitRedirect/receiveSSORequest.dispatch'
SAML message intended destination endpoint did not match recipient endpoint

where SPInitRedirect is Controller
          receiveSSORequest is Action
          940iuuikfpkqru5l is Id

When the checkEndpointURI does a httpRequest.getRequestURL(), the url returned has /grails and .dispatch and the id is not there. That is how the grails request URL looks like.

So the validation of the request fails

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20130827/b3cea11b/attachment.html