From: D B. <ba...@aw...> - 2017-11-03 09:36:33
|
Hi, thanks! Setting unityServer.core.httpServer.advertisedHost=192.168.1.100:2443 in ${CONF}/unityServer.conf indeed fixed the issue. Cheers, D On 25/10/17 16:43, Krzysztof Benedyczak wrote: > Hi, > > W dniu 24.10.2017 o 16:21, D Baum pisze: >> Hi, >> >> I'm trying to setup up Unity as a SAML hub/bridge by connecting it to an >> upstream Shibboleth SAML IdP. >> >> I first tried this while running unity on the preconfigured port 2443 - >> but I noticed that the sp xml configuration file and the AuthnRequests >> generated by Unity don't specify the port in URLs. >> After I logged in with the IdP, this led to a timeout when my browser >> was redirected to unity's AssertionConsumerService - which couldn't be >> found at the given URL since the port wasn't correct. >> >> Is this intentional? If so, can the port of unity's SAML SP consumers be >> configured and how? > > Most likely you didn't set properly the advertisedHost address in the > main unityServer.conf. It is used as a base, and Unity can not guess it > as may be behind proxy/fw. > > HTH > Krzysztof |