Shibboleth SAML in non Standard Ports (https)

[Nate Klingenstein]

Andrés,

You should only need to configure your servlet container to listen on the non-standard port(e.g. an SSL connector listening on 9443) and your IdP metadata(specifically, the SingleSignOnService endpoints) needs to match.  e.g.

<EntityDescriptor entityID="https://ndk.shibathome.lalala/idp/shibboleth">

…

<SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://ndk.shibathome.lalala:9443/idp/profile/SAML2/Redirect/SSO"/>

You’ll also have to watch out for firewalls in the intermediate networks, of course.

Hope this helps,
Nate.

On Apr 25, 2015, at 8:58 AM, Andrés Yacopino <ayacopino at gmail.com<mailto:ayacopino at gmail.com>> wrote:

Hi, I am new with Shibboleth and SAML, trying to deploy a Shibboleth SAML IDP internally to be integrated with and external Service Provider (SP).
We have a firewall to internet and we are already using port 443 (https) in the firewall redirecting to also port 443 to an internal server.

So only having 1 external Static IP to Internet so I can't use port 443 for Shibboleth.

I am seeing that in metadata.xml port 8443 and 443 exists.
I have imported SP metadata and send our metadata to SP, but it seems in testing (one url that SP has sent), it is trying to connect to port 443.


The question is, what changes I need to do to make Shibboleth works in non standard port 443?

Thanks for the help.

--
Andrés Yacopino
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net<mailto:users-unsubscribe at shibboleth.net>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150425/df717661/attachment.html>