Upgrading from OpenSAMLv2.6.1 to OpenSAMLv2.6.4 resulting in SSL peer failed

[Brent Putman]

On 8/22/16 5:43 AM, punit ashra wrote:
> Hi Dev Team,
>
> I am upgrading from OpenSAMLv2.6.1 to OpenSAMLv2.6.4, i am getting 
> SSL peer failed hostname validation for name: null
>
> Stacktrace:-
>
> Caused by: javax.net.ssl.SSLPeerUnverifiedException: SSL peer failed
> hostname validation for name: null
> at
> org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.verifyHostname(TLSProtocolSocketFactory.java:233)
> at
> org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.createSocket(TLSProtocolSocketFactory.java:194)
> at
> org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
>
>
>

It's a bug that is misreporting an earlier failure:

https://issues.shibboleth.net/jira/browse/JOWS-44

It was fixed in the last 2.x release, v2.6.6.  That will likely not
"fix" the problem, since you likely have another PKIX or other TLS
error going on, but it will eliminate the erroneous error message.

And of course 2.x is end-of-life now, so you should really start
thinking about upgrading to 3.x.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20160822/9fcc2502/attachment.html>