Go to All Forums

APM Insight .NET agent - Do not disable TLS 1.0/1.1

Disabling TLS 1.0/1.1 renders the APM Insight .NET agent completely useless.

We had to disable TLS 1.0/1.1 last week to adhere to our payment gateway provider's guidelines. It should have already been disabled, but the app developer forgot to mention it.

Once TLS 1.0/1.1 are disabled, the APM Insight .NET agent no longer functions. The services starts and runs, but is unable to establish a connection - "(Could not create SSL/TLS secure channel).

I worked with Site4x7 support this morning and there is no fix until they recompile with the latest .Net version with TLS 1.2 support.

I haven't found anything in the documentation that states TLS 1.0/1.1 are required, but this is a setback for us. We can't enable TLS 1.0/1.1 and we now have limited monitoring/insight into the .Net apps.

Hoping they can get a new version released soon.

 

 

Reply 3
Replies (2)

Re: APM Insight .NET agent - Do not disable TLS 1.0/1.1

by SSS1

Dear Bruce, 

Thanks for posting it here. Just an update on the progress. 

We have recompiled our dotnet agent in .NET 4.5. We were successfully able to monitor applications running in .NET 4.0 and above. However, we couldn't do the same for applications running in lower versions of the .NET CLR. Due to this, we couldn't include this change in our upcoming release. We'll update it here in the community once it goes live.

In the meanwhile, if you have disabled TLS 1.0 in your servers and require a TLS 1.2 compatible version of .NET Agent, kindly contact support. We would be able to share a beta version of the agent and assist in troubleshooting. 

Thanks & Regards,

Shrinivasan S S

Developer, APM Insight .NET Agent

Reply 1

Re: Re: APM Insight .NET agent - Do not disable TLS 1.0/1.1

Hi, Shrinivasan.

I worked with support on Tuesday to get the APM beta version installed and I'm happy to report that APM agent 3.8 is working with TLS 1.0/1.1 disabled.

It took a couple of weeks to get the issue resolved, but I understand the agent had to be recompiled with a newer .Net version so I appreciate the support team responding and resolving this issue in a timely manner.

Reply 4