Apache mod_proxy, Jetty, and IDP endopint problem

[Wessel, Keith]

Hi,

As part of our IDP v3 upgrade, we're making the long overdue move from Tomcat to Jetty. We still want to leave Apache in front of things, though, since it's well integrated into our environment. So, I'm using mod_proxy_http to proxy things to Jetty. I'm using an http connection to port 8080. I suspect, though, that the non-https transport on the proxy eonnection is breaking the endpoint check from the IDP, though:

2015-06-10 15:11:46,769 - ERROR [org.opensaml.saml.common.binding.security.impl.ReceivedEndpointSecurityHandler:199] - Message Handler:  SAML message intended destination endpoint ' 
https://shibboleth-test.techservices.illinois.edu/idp/profile/SAML2/Redirect/SSO' 
 did not match the recipient endpoint ' ht tp://shibboleth-test.techservices.illinois.edu/idp/profile/SAML2/Redirect/SSO'

Only reason I doubt my theory is that the log doesn't say anything about http://localhost:8080 or something like that. It has the right host and port, just the wrong transport. Is something else broken? Or does my theory seem right, and do I need to really use an https link between Apache and Jetty on localhost?

Thanks,
Keith