What determines protocol of SAML2/POST assertion?

[Spencer Gaddy]

Hi, I am working on a Shibboleth native 2.0 SP setup and having a bit of
trouble after setting up all my load balancers and url rewrite rules.

Essentially we are getting assertions back to our SP endpoint over http,
but we do not accept http on our front end load balancer.

We are seeing the following error after logging in to any IDP and the
assertion comes back.

To report this problem, please contact the site administrator at
root at localhost. Please include the following message in any email:
opensaml::BindingException at (http://${ourHost}.com/auth/shib/SAML2/POST)
SAML message delivered with POST to incorrect server URL.

The odd thing about this is that we have specifically set the endpoint as
https in our metadata file. As per below.

<md:AssertionConsumerService
Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
Location="https://${ourHost}/auth/shib/SAML2/POST"
index="1"/>

So my question is even though we are specifying the location as https why
are we getting assertions back on http?

Thanks in advance for the help.
​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20150304/dd6604fd/attachment.html