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

[Philip Durbin]

Hello Shibboleth enthusiasts!

I'm confused about this error from
http://idp.testshib.org/cgi-bin/idplog.cgi?lines=300

13:30:18.631 - WARN
[org.opensaml.saml2.binding.AuthnResponseEndpointSelector:206] -
Relying party 'https://shibtest.dataverse.org/shibboleth' requested
the response to be returned to endpoint with ACS URL
'https://shibtest.dataverse.org/Shibboleth.sso/SAML2/POST'  and
binding 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST' however no
endpoint, with that URL and using a supported binding,  can be found
in the relying party's metadata

Confused because the metadata I just uploaded to
http://testshib.org/register.html has the port number "9999" in it:

$ grep SAML2/POST\" shibtest.dataverse.org
    <md:AssertionConsumerService
Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
Location="https://shibtest.dataverse.org:9999/Shibboleth.sso/SAML2/POST"
index="1"/>

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?

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

Thanks!

Phil

p.s. More of my sad, sad story:
https://docs.google.com/document/d/1DdLVuh8_e_2DINO1xCTj28h35cAwnD0QdevOnEuTo_I/edit?usp=sharing

-- 
Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin