Multiple Vhosts - one end point

[Aaron Roots]

Howdy,

We are setting up a server that provides hosting for different areas
within our University. We are looking to provide Shibboleth as the
authentication method. However I am not wanting to have to configure
Shibboleth for every new vhost that gets set up. Reading through the doco
­ it sounds like this is possible ­ I have had a go at configuring the SP
­ however I am getting the following errors in the IdP logs:

2011-10-07 16:41:24.143 - WARN
[org.opensaml.saml2.binding.AuthnResponseEndpointSelector:203] - Relying
party 'https://example.edu.au/shibboleth
' requested the response to be returned to endpoint with ACS URL
'http://vhost1.example.edu.au/Shibboleth.sso/SAML2/POST'  and binding
'urn:oasi
s: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 
2011-10-07 16:41:24.143 - ERROR
[edu.internet2.middleware.shibboleth.idp.profile.AbstractSAMLProfileHandler
:429] - No return endpoint available for relying pa
rty https://example.edu.au/shibboleth



So the vhost1.example.edu.au is being sent by the SP as the return path ­
and gets that from the Server Name parameter in the apache vhost config.

However the end points that are being passed in the metadata are all under
http://example.edu.au/Shibboleth.sso/

I thought the following would help me in the shibboleth2.xml ­ I thought
by default it must automatically chose separate end points ­ and I should
force all hosts to use the one entityID configuration
<RequestMapper type="Native">
        <RequestMap applicationId="default">
           <HostRegex regex="^.*$" applicationId="onetomany"/>
        </RequestMap>
    </RequestMapper>

ŠŠ
        <ApplicationOverride id="onetomany"
entityID="https://example.edu.au/shibboleth"/>




And trying to specify the full URL it in the ACS only made endpoints be a
bit crazy
<md:AssertionConsumerService
Location="https://example.edu.au/Shibboleth.sso/SAML2/POST" index="1"
                Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"/>



Wondering if anyone could provide some further pointers - or let me know
how I am way off track
Cheers heaps
Aaron