SAML message intended destination endpoint did not match the recipient endpoint

[Ryan Suarez]

On 7/11/16, 4:41 PM, "users on behalf of Ryan Suarez" <users-bounces at shibboleth.net<mailto:users-bounces at shibboleth.net> on behalf of ryan.suarez at sheridancollege.ca<mailto:ryan.suarez at sheridancollege.ca>> wrote:

This is my shibboleth-identity-provider-3.2.1/embedded/jetty-base/etc/jetty.xml:

Again, I don't know what you specifically are doing, but you should not in general be using anything there. That's not for you, it's for our Windows installer. It will be gone in the next release to get rid of this confusion.

Is this the right place to put the x-forward-for configuration?

If you point JETTY_BASE at that directory, then I'm not saying it wouldn't get used, but you wouldn't in general be expected to have done that.

So sure, that could well be the problem, maybe you're editing stuff that doesn't have anything to do with your Jetty deployment.

Ok, so that was the problem.  I was mistakenly configuring the embedded jetty config file, not aware that this is for Windows only.

Confusion stems from archived posts:
http://shibboleth.net/pipermail/users/2015-April/021087.html
"It was in the delivered jetty.xml, just commented out and waiting for me to find it.”

…and wiki doc:
https://wiki.shibboleth.net/confluence/display/IDP30/Running+the+IdP+on+Jetty+behind+Apache+httpd
"This is done in jetty.xml”
"On my installation of Jetty, this block was already in the config file, and I just had to uncomment it.”

…and my unfamiliarity with Jetty (I’m coming from shib2/tomcat).  The only jetty.xml I could find with the commented out proxy/forwarding options was on the embedded/jetty-base on the shib tarball.

Thanks for the clarification.

Regards,
Ryan


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160712/66676fd4/attachment.html>