<div dir="ltr">Scott:<div><br></div><div>Thank you so much! Appreciate your response. As you suggested, I have appended the :443 to the server name in the sites-<name>.conf which resolved the issue. The metadata location is now generated without any port number <a href="https://server.name1/Shibboleth.sso/SAML2/POST" target="_blank" style="font-size:13px">https://server.name1/Shibboleth.sso/SAML2/POST</a><span style="font-size:13px;color:rgb(80,0,80)"> .</span></div><div><span style="font-size:13px;color:rgb(80,0,80)"><br></span></div><div><span style="font-size:13px;color:rgb(80,0,80)">Thanks</span></div><div><span style="font-size:13px;color:rgb(80,0,80)"><br></span></div><div><span style="font-size:13px;color:rgb(80,0,80)">Nara</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 16, 2015 at 11:07 AM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2/16/15, 6:41 PM, "nr673 ." <<a href="mailto:nara.rama.us@gmail.com">nara.rama.us@gmail.com</a>> wrote:<br>
><br>
>In my environment, the Apache server is configured to accept the SSL<br>
>connection only with the empty port or default port 443.<br>
<br>
</span>That isn't the sum total of your configuration, you're SSL offloading<br>
and/or virtualizing in some way, and that creates requirements for your<br>
Apache options like ServerName.<br>
<span class=""><br>
>So, I configured the post back URL in OKTA(IdP) as<br>
><a href="https://server.name1/Shibboleth.sso/SAML2/POST" target="_blank">https://server.name1/Shibboleth.sso/SAML2/POST</a><br>
</span>><<a href="https://server.name1/Shibboleth.sso/SAML2/POST" target="_blank">https://server.name1/Shibboleth.sso/SAML2/POST</a>>. But, the shibboleth<br>
<span class="">>generates the POST url with the default port number as<br>
><a href="https://server.name1:80/Shibboleth.sso/SAML2/POST" target="_blank">https://server.name1:80/Shibboleth.sso/SAML2/POST</a>. This url mismatch<br>
>results in the BindingException.<br>
<br>
</span>Which is because your web server is broken, per above. You're accessing it<br>
in a manner that makes it believe its port is 80 so that's what it<br>
generates. Your ServerName probably needs :443 in it.<br>
<span class=""><br>
>So, I want to modify the URL generated by Shibboleth. Since the<br>
>handlerURL accepts only the relative value, I cannot make the Shibboleth<br>
>to generate either<br>
><a href="https://server.name1/Shibboleth.sso/SAML2/POST" target="_blank">https://server.name1/Shibboleth.sso/SAML2/POST</a> or<br>
><a href="https://server.name1:443/Shibboleth.sso/SAML2/POST" target="_blank">https://server.name1:443/Shibboleth.sso/SAML2/POST</a>.<br>
<br>
</span>It doesn't just accept a relative value, and in any case that is *not* the<br>
fix. Your web server configuration is wrong and needs to be properly<br>
virtualized so that the logical port and scheme are overriding the<br>
physical ones the server sees.<br>
<div class="HOEnZb"><div class="h5"><br>
-- Scott<br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</div></div></blockquote></div><br></div>