<div dir="ltr">Well I removed all the irrelevant stuff per your recommendation.<div style>Removed all the added stuff from Shibboleth.xml</div><div style>Started fresh on the IdP by regenerating the Metadata from the SP and adding the ACS URLs + upped their indexes.<br>
</div><div style><br></div><div style>Now I think the last point is httpd.conf. this is what I left:</div><div style><div><VirtualHost <a href="http://new-host.example.com:443">new-host.example.com:443</a>></div><div>
ServerName new-host.examplecom:443</div><div>ServerAlias new-host.examplecom</div><div>UseCanonicalName On</div><div></VirtualHost></div><div><br></div><div style>I am trying without Location and the applicationId as you mentioned.</div>
<div style>am I using the directives correctly?</div><div style>And another question is how should the Virtualhost do the binding? on port 443 which is what the Load Balancer is listening on? or maybe 8080 since this is what the Application is listening to (so maybe <VirtualHost <a href="http://new-host.example.com:8080">new-host.example.com:8080</a>> ? that doesn't seem to work as well...</div>
<div style><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 11, 2013 at 2:01 PM, Peter Schober <span dir="ltr"><<a href="mailto:peter.schober@univie.ac.at" target="_blank">peter.schober@univie.ac.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">* Ran <<a href="mailto:ran@sheinberg.net">ran@sheinberg.net</a>> [2013-03-11 12:44]:<br>
<div class="im">> > Since you're using Apache httpd there's nothing in the SP you'd *need*<br>
> > to change, in the most common case (so using overrides wouldn't be my<br>
> > first choice). Instead you could simply configure the second virtual<br>
> > host correctly in Apache httpd, by setting ServerName.<br>
><br>
> -- Didn't I do that? can you point out what's wrong in the snippet from<br>
> httpd.conf?<br>
<br>
</div>Yes, but you also set an application id (I'd try without<br>
ApplicationOverrides first) so remoev that. And there were the changes<br>
to shibboleth2.xml (which I said you don't need.)<br>
<div class="im"><br>
> > For response messages from the IdP to be able to be recieved correctly<br>
> > you'd then put additional protocol endpoints (ACS URLs etc) for the<br>
> > new vhost into the same EntityDescriptor for the existing SP. Done.<br>
> ><br>
> > -- Didn't I do that as well? added<br>
> <md:AssertionConsumerService<br>
> Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="<br>
> <a href="https://new-host.example.com/Shibboleth.sso/SAML2/POST" target="_blank">https://new-host.example.com/Shibboleth.sso/SAML2/POST</a>" index="1"/><br>
> In the SP's metadata file that is located on the IdP.<br>
<br>
</div>That should do. Provided the IdP has fresh metadata (otherwise it will<br>
fail anyway) I'd make sure any index values from ACS URLs are unique.<br>
Then look at your logs.<br>
<div class="HOEnZb"><div class="h5">-peter<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>