Running mod_shib on a non-standard port (i.e. 9999 rather than 443)

[Cantor, Scott]

On 4/28/15, 1:50 PM, "Philip Durbin" <philip_durbin at harvard.edu> wrote:

>Here are my questions:
>
>1. Why is TestShib trying to use
>https://shibtest.dataverse.org/Shibboleth.sso/SAML2/POST rather than
>https://shibtest.dataverse.org:9999/Shibboleth.sso/SAML2/POST when the
>port (9999) is in my metadata?

Your metadata is what it checks against, the URL is in the AuthnRequest.

>2. Does anyone in the world run mod_shib on a non-standard port like this?

Yes. Your web server believes it's running on port 443 based on the request asking for that URL. Shibboleth has literally no role here, not for an Apache deploy. The URL is built from standard Apache API calls for the scheme, name, and port.

-- Scott