How does SoapUI bypass Certificate errors and SSL issues?

We have a C# .NET solution we're attempting to create to allow a client to utilize an old and insecure SSL web service. (I have done some considerable research into why there is issues, and it seems to stem from the fact that Microsoft and many others have deprecated and unsupported 512 encryption for SSL web services). What we found in our testing though, is that SoapUI is able to retrieve the response without issue, whereas any other client will return the error: "The underlying connection was closed: An unexpected error occurred on a send."

How does SoapUI bypass this issue, and how can we recreate this functionality?