Was there any big change put in production this weekend? Regarding TLS

[rickwolff]

Hello, I started getting the following exception this weekend after users log in:
" The request was aborted: Could not create SSL/TLS secure channel. "

Was there any big change that was published to production this weekend?

Was it the one discussed below?

Action Required: Upgrade to TLS 1.2 or later

hi everyone, I have received a notification from Auth0 system stated that I need to stop using old TLS 1 and 1.1 protocol. They stated the reason I am receiving this is that internal traffic analysis showed there are tenants still using it. How can we check and how can I disable it to force only TLS1.2? I don’t have the custom domain within tenants. Many thanks.

Thanks!

[dan.woda]

Hi @rickwolff,

It looks like the TLS updates started rolling out a couple of weeks ago, it may have to do with that. Do you know if any of your clients are using the unsupported TLS versions 1.0 or 1.1?

[rickwolff]

We’ve found a way to fix that.
On LoginCallback.ashx.cs we put the line below before calling the httpClient.GetTokenAsync:

ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3 | SecurityProtocolType.Tls | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12;

Then it solved the issue. But our system was down for some time because of it and I wasn’t understanding the reason.

I’ll leave it here so it may help someone else as well. But I think it was strange that I didn’t receive any notification on my auth0 notifications panel.

Thanks

[dan.woda]

It looks like most users who were using the older TLS versions would receive an email notice. Regardless, thank you for posting a solution and update, and thanks for your patience on this.