What determines protocol of SAML2/POST assertion?

[Spencer Gaddy]

ahhhh, yes my understanding was that the metadata file was what impacted
the location the post assertion comes to, I see how that is incorrect now.

One quick issue now is that with this URL schema, set to `ShibURLScheme
https` I get the post back to my host and it is specifying manually port
80, like below.

`opensaml::BindingException at (https://${myHost}:80/auth/shib/SAML2/POST)`

How is port determined? And how can we force it to be 443?

Thanks again for the help.



On Wed, Mar 4, 2015 at 11:20 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 3/4/15, 7:09 PM, "Spencer Gaddy" <recneps at gmail.com> wrote:
>
>
>
> >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.
>
> Because you haven't actually done that step fully.
>
> https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPNoSSL
>
> >Essentially we are getting assertions back to our SP endpoint over http,
> >but we do not accept http on our front end load balancer.
>
> No, that's not the case. You're getting them over http physically and your
> web server does not know that it's been virtualized and should be treating
> them as https.
>
> >The odd thing about this is that we have specifically set the endpoint as
> >https in our metadata file. As per below.
>
> Metadata does not control how web servers interpret their requests and
> report URLs.
>
> -- Scott
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20150304/2546fa0f/attachment.html