#1 2019-06-28 17:15:12

Burt C

Keeping up with SSL

This is just an FYI post for those who may be like my organization running old code targetting the 2.0 .NET framework or anything prior to 4.6.  On 6/16/2019 something changed on the Adobe Connect Servers (likely they just did a normal Windows Update/Patch to disable outdated SSL 3 and TLS 1.0 security protocols on their servers) and I had to update my targetted framework to 4.6.  On one of my servers I didn't already have the 4.6 framework installed so I targetted 4.5.2 and added one line of code to permit login and all other API commands to work:

System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12;

Prior to updating all attempts to login resulted in a

"The underlying connection was closed: an unexpected error occurred on a send."

error.  Now I suspect I'm the only person supporting old code like this, but I posted this just in case.

Jorma_at_CoSo

Re: Keeping up with SSL

Thanks for sharing. Here's the post about the depreciation of TLS 1.0 in the hosted environment.

https://blogs.adobe.com/connectsupport/ … r-tls-1-0/

---

CoSo Cloud
Adobe Certified Instructor