Home → Web Services →

Authentication handshake has stopped working

• Edit

thugsb

Nov 19, 2014 @ 09:17 PM

Our WSDL scripts have stopped working. They stopped working on 2014-10-28, yet our last server upgrade was in August. Our server is running 7.12.1.

We have some fairly complex scripts, which are all available here: https://github.com/thugsb/wsdl-cascade with readSingleAsset.php being a simple script that I've been using for testing.

However, running the most basic sample script (https://github.com/hannonhill/Webservices-PHP-Sample-Project/blob/m...) produces this error:

Fatal error:  Uncaught SoapFault exception: [soapenv:Server.generalException] Validation error: Received fatal alert: handshake_failure; nested exception is: 
    java.lang.Exception: Validation error: Received fatal alert: handshake_failure in /Users/stu/Sites/web-services/read.php:16
Stack trace:
#0 /Users/stu/Sites/web-services/read.php(16): SoapClient->__call('read', Array)
#1 /Users/stu/Sites/web-services/read.php(16): SoapClient->read(Array)
#2 {main}
  thrown in /Users/stu/Sites/web-services/read.php on line 16

This handshake error is the same error that I'm getting with all of my other scripts.

https://{removed}:8443/ws/services/AssetOperationService?wsdl seems to be working, and doesn't seem to have changed the auth mechanism at all. So I'm at a loss as to what the problem is. Do you have any idea? Thanks!

1. Support Staff 1 Posted by Tim on Nov 19, 2014 @ 09:24 PM

   

   Hi,

   Can you reproduce the behavior in your instance and then immediately grab and upload the latest cascade.log file? I want to see if there is a stack trace for the error message you included above.

   Thanks!

   • Edit

2. 2 Posted by thugsb on Nov 19, 2014 @ 09:43 PM

   

   Nothing is coming up in the cascade.log. It seems that the request isn't even getting that far.

   Doing some research, it looks like this thread might hold some answers: http://stackoverflow.com/questions/6353849/received-fatal-alert-han...

   It's possible we've got an old version of SSL on the cascade server, and so the request is simply failing before it even gets to talk to the server. I'll keep this thread updated if we make any progress...

   • Edit

3. Support Staff 3 Posted by Tim on Jan 06, 2015 @ 07:22 PM

   

   Hey there,

   Just checking in to see if you were ever able to resolve this particular issue. Let me know!

   Thanks

   • Edit

4. 4 Posted by thugsb on Jan 06, 2015 @ 08:23 PM

   

   Yes, this was to do with an out-of-date version of SSL. Once that was updated, everything worked again. :)

   • Edit

5. thugsb closed this discussion on Jan 06, 2015 @ 08:23 PM.