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
Azure going to enforce 1.2 starting June 30, 2020. It's important to make sure that HDInsight environments are ready:
Starting on June 30, 2020, Azure HDInsight will enforce TLS 1.2 or later versions for all HTTPS connections. We recommend that you ensure that all your clients are ready to handle TLS 1.2 or later versions. For more information, see Azure HDInsight TLS 1.2 Enforcement.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
May 13, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
HDInisght supports specifying [minimum TLS version]https://docs.microsoft.com/en-us/azure/hdinsight/hdinsight-plan-virtual-network-deployment#transport-layer-security). Supported values 1.0, 1.1 and 1.2.
Azure going to enforce 1.2 starting June 30, 2020. It's important to make sure that HDInsight environments are ready:
New or Affected Resource(s)
Potential Terraform Configuration
The text was updated successfully, but these errors were encountered: