You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the upcoming depreciation of TLS 1.0 and 1.1 on 31st October, do we expect any of the core Umbraco packages to be affected, I'm thinking around the file providers for Blob on V7 and V8?
The text was updated successfully, but these errors were encountered:
For V7 and 4.5.2, and you basically just need to programmatically enforce TLS-1.2 as the default HTTP Security - and that should then allow requests to services only accepting TLS-1.2 - I've had it working with Azure-BlobStorage for ages. Azure-REDIS is a bit trickier, but can also be done on V7.
Something like this in your ApplicationStarting event: if (!System.Net.ServicePointManager.SecurityProtocol.HasFlag(System.Net.SecurityProtocolType.Tls12)) { System.Net.ServicePointManager.SecurityProtocol = System.Net.ServicePointManager.SecurityProtocol | System.Net.SecurityProtocolType.Tls12; }
For V8 I believe that there is a config option for that in Dot.Net 4.7.2 (?)
With the upcoming depreciation of TLS 1.0 and 1.1 on 31st October, do we expect any of the core Umbraco packages to be affected, I'm thinking around the file providers for Blob on V7 and V8?
The text was updated successfully, but these errors were encountered: