SP with multiple Tomcat instances

jp james.pittard at dsainc.com
Mon Jan 15 10:35:57 EST 2018


I have a Shibboleth 3.3.1 IDP running, and a Shibboleth 2.6.1 SP. The SP is
running with Apache connected to Tomcat with a ProxyPass setting to Tomcat
on AJP. It works great when connected to a single Tomcat instance.

I am now trying to get the SP set up to function for multiple Tomcat
instances on the same server, each running on a different port. I found this
that may be relevant, but I may not be understanding it correctly:
https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPApplicationOverride#NativeSPApplicationOverride-Hostvs.Path.

For one of the Tomcat installations running AJP on port 8011, I have added a
VirtualHost in Apache httpd listening on port 7445. I set ServerName to
hostname:7445 in the VirtualHost. Now when I go to
https://hostname:7445/context, I get the following on the IDP:

2018-01-15 10:31:56,300 - WARN
[net.shibboleth.idp.saml.profile.impl.PopulateBindingAndEndpointContexts:410]
- Profile Action PopulateBindingAndEndpointContexts: Unable to resolve
outbound message endpoint for relying party 'https://hostname/shibboleth':
EndpointCriterion
[type={urn:oasis:names:tc:SAML:2.0:metadata}AssertionConsumerService,
Binding=urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST,
Location=https://hostname:7445/Shibboleth.sso/SAML2/POST, trusted=false]

I am using fixed files for metadata, and I tried setting up an additional
copy of the metadata with entityID=https://hostname:7445/shibboleth, with no
change.

Now I'm stuck. Suggestions?



--
Sent from: http://shibboleth.1660669.n2.nabble.com/Shibboleth-Users-f1660767.html


More information about the users mailing list