Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure TLS 1.0 & 1.1 Depreciation - Any expected package issues? #240

Open
AaronSadlerUK opened this issue Sep 19, 2024 · 1 comment
Open

Comments

@AaronSadlerUK
Copy link

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?

@c9mb
Copy link

c9mb commented Sep 19, 2024

I think that's more of a Dot.Net thing.

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 (?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants