Shib IDP's LDAPS attribute resolution and SSLv3

[Wessel, Keith]

Sorry, Nate, host.name.removed was me. I pull out our real ldap server hostname before posting to the list.

We are running V2.4.2 as of this past Monday, so that's not the case here.

Keith


From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Nate Klingenstein
Sent: Wednesday, October 15, 2014 2:36 PM
To: Shib Users
Subject: Re: Shib IDP's LDAPS attribute resolution and SSLv3

Keith,

I'd start my investigation with the hostname checks that Shibboleth had to add recently.  host.name.removed is pretty suspicious, but I don't know where that code is.  It's the first thing I'd look for.

http://shibboleth.net/community/advisories/secadv_20140919.txt

Dunno,
Nate.

On Oct 15, 2014, at 1:30 PM, Wessel, Keith <kwessel at illinois.edu<mailto:kwessel at illinois.edu>> wrote:


13:44:08.766 - ERROR [edu.vt.middleware.ldap.pool.DefaultLdapFactory:109] [session=296a318ae3b59564bf94f8fb50fee6ef4a93ecd3716f7574556b0a6715c65b97]
- unabled to connect to the ldap
javax.naming.ServiceUnavailableException: host.name.removed:636; socket closed


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20141015/22af44fc/attachment.html