1
votes

The UPS API is switching over to a mandated TLS 1.2 protocol. We have asp.net 2.x applications using that API and as of May 31st they're going to stop working. Actually, they warned us that we would start experiencing outages up until that date which we are currently experiencing.

The app is running on IIS7, Windows 2k8 R2. I would switch IIS to use TLS 1.2 but we have people consuming our old asp.net 2.x web services and that would cause the same issue for them if we switched over.

Is it possible to set just a single site or pool to use TLS 1.2, but not change it globally?

Our last resort is to write a proxy app in asp.net 4.5. We'll call this proxy from our 2.x code and then have it call the UPS services. I was seeing if there was an easier way to avoid writing this code and figuring out a way to do it in server configuration.

1

1 Answers

0
votes

I was able to add registry settings on my web service to enable TLS 1.2 (and 1.1). Leaving the old SSL keys allowed me to support them all and it has not adversely affected my current applications. However, it has completely solved my issue with the UPS web service.

I used the settings in this article Enable TLS on Windows Server and IIS