For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

bluzdoggy_17129's avatar
bluzdoggy_17129
Icon for Nimbostratus rankNimbostratus
Oct 07, 2016

I have been diligently working on this. I also have a ticket open with F5. SSL dumps show a valid 3 way handshake. I believe there is an issue with something regarding the transition from the client ssl to the server ssl. I see a 404 error from the broker when it sends back to the F5:

 

HTTP/1.1 404 Not Found

 

As the connection continues to try to complete the logs show the F5 assigning a "fake" GUID in the xml file that it wants to pass to the broker:

 

aaaaaaaa-bbbb-cccc-ddddddddddddddddd

 

Any time I go straight to the broker from the client (F5 not in the signal path) there is no issue with the connection.