i figured it out .Net core 3.1 bluster slim base image has dropped support for tls 1.0 and 1.1 by default only tls 1.2 is enabled.
we can confirm it by /etc/ssl/openssl.cnf file in base image.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
From aspnet core 3.1 linux container hosted in aks I am calling azure sql server and azure redis cache. can u tell me how I can prove my client is using tls1.2 while on azure sql server tls 1.0 1.1 and 1.2 in enabled. On Azure Sql server i have not enabled minimum tls version.
Redis cache also support tls.1.0 1.1 and 1.2 there is no minimum tls version supported feature on azure redis cache.
I am using entity framework core 3.1.
i want verification from client side.
I need this for my audit
i figured it out .Net core 3.1 bluster slim base image has dropped support for tls 1.0 and 1.1 by default only tls 1.2 is enabled.
we can confirm it by /etc/ssl/openssl.cnf file in base image.
Hello @Somnath Shukla , I researched more on this and I see that this is application specific and needs dedicated troubleshooting. Our backend AKS or database logs might help. Hence I would request you to open a support ticket with Microsoft Support if you have a subscription which allows you to do so. Otherwise , you can send an email with subject line “Attn:Jaya” to AzCommunity[at]Microsoft[dot]com referencing this thread along with the subscription id.