Shibboleth SP Ports

[Scott Klawitter]

>> Uh, no, do NOT open 1600. It shouldn't matter assuming it's bound to
localhost, but don't invite trouble certainly. That protocol is NOT
secured.

I just noticed the binding you were referring to:

<TCPListener address="127.0.0.1" port="1600" acl="127.0.0.1"/>

https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPTCPListener

Thanks,

Scott K

-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net]
On Behalf Of Cantor, Scott
Sent: Friday, November 18, 2011 4:19 PM
To: users at shibboleth.net
Subject: Re: Shibboleth SP Ports

On 11/18/11 5:09 PM, "Scott Klawitter" <sklawitter at ebsco.com> wrote:

>Does anyone have a list of ports that should be open for a Server to 
>successfully run a Shibboleth SP configuration?

Nothing whatsoever. Other than your web service anyway.

>I am aware of:
>
>    443
>    80
>    1600 (shibd)

Uh, no, do NOT open 1600. It shouldn't matter assuming it's bound to
localhost, but don't invite trouble certainly. That protocol is NOT
secured.

>    ? (ntp service)

NTP calls out as far as I know, not in.

-- Scott

--
To unsubscribe from this list send an email to
users-unsubscribe at shibboleth.net