# TLS 1.0 still enabled after setting tls\_policy to recommended

**URL:** <https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008>\
**Category:** Get Help\
**Tags:** security, tls\
**Created:** [July 27, 2020, 5:57pm UTC](https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008 "2020-07-27T17:57:02Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![paolodm](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/paolodm/32/22795_2.png) [@paolodm](https://community.auth0.com/u/paolodm)\
**Post date:** [July 27, 2020, 5:57pm UTC](https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008/1 "2020-07-27T17:57:02Z")

</div>

I am looking to disable TLS 1.0 and 1.1 for my custom domain. I followed the recommendation in [http://community.auth0.com/t/how-can-i-disable-tls-1-0-tls-1-1-and-weak-ciphers-with-custom-domains/45078](http://community.auth0.com/t/how-can-i-disable-tls-1-0-tls-1-1-and-weak-ciphers-with-custom-domains/45078) by setting tls\_policy to `recommended`.

It did disable TLS 1.1; however, TLS 1.0 is still enabled. How do I completely downgrade support for both these older TLS versions?

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [July 28, 2020, 12:20pm UTC](https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008/3 "2020-07-28T12:20:34Z")

</div>

Thanks for reporting that. I’ll look into that and will get back to you shortly!

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [July 31, 2020, 2:33pm UTC](https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008/4 "2020-07-31T14:33:38Z")

</div>

Hey there!

I was asked to have your tenant name to perform some checks. Can you send it to me via private message? Thank you!

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [August 3, 2020, 9:40am UTC](https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008/5 "2020-08-03T09:40:52Z")

</div>

Hey there!

Have you had a chance to check out my last message? Thank you!

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [August 5, 2020, 4:18pm UTC](https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008/6 "2020-08-05T16:18:40Z")

</div>

**Solution**

`"tls_policy":"recommended"` instead of `"tls_policy":"compatible"`

---

<div class="post-metadata">

**Author:** ![matt.macadam](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/matt.macadam/32/55188_2.png) [@matt.macadam](https://community.auth0.com/u/matt.macadam)\
**Post date:** [August 11, 2020, 4:16pm UTC](https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008/7 "2020-08-11T16:16:39Z")

</div>

Hello,

I have some additional detail around this. Depending on how you’re checking for TLS 1.0 and 1.1 support it can _appear_ to still be enabled after changing the policy via the management API, particularly if you are using the SSL Labs tool (it’s a great tool but it’s not always 100% clear what it is doing).

SSL Labs is checking for TLS protocol support with and without SNI (Server Name Indication). Our configuration flag disables TLS 1.0/1.1 only for requests to your domain, as indicated by SNI in the TLS handshake. The “default” domain that you would reach without SNI will still allow you to negotiate a TLS 1.0 connection (the default domain does not have a valid certificate so that’s not very useful).

You can see this with OpenSSL when you try to force a TLSv1/1.1 connection for your domain with SNI (-servername does SNI for the indicated domain and -tls1 and -tls1\_1 forces TLSv1 and v1.1, respectively):

openssl s\_client -connect my.custom.domain:443 -servername my.custom.domain -tls1

and  
openssl s\_client -connect my.custom.domain:443 -servername my.custom.domain -tls1\_1

(I won’t include the output here as it’s messy, but the result is a handshake failure for both TLS versions)

And then try:

openssl s\_client -connect my.custom.domain:443 -tls1

That does TLSv1 without SNI–the handshake succeeds but from the TLS perspective there is no hostname context, so you get the server’s default certificate (it’s self-signed and expired since it’s not actually used). A connection without SNI can’t be used to interact with your tenant.

I hope that helps clear this up.

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [August 12, 2020, 11:44am UTC](https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008/8 "2020-08-12T11:44:12Z")

</div>

Thanks for clarifying that Matt!

---

<div class="post-metadata">

**Author:** ![paolodm](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/paolodm/32/22795_2.png) [@paolodm](https://community.auth0.com/u/paolodm)\
**Post date:** [August 12, 2020, 1:10pm UTC](https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008/9 "2020-08-12T13:10:15Z")

</div>

Thanks Matt and Konrad. We will look into this.

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [August 12, 2020, 2:35pm UTC](https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008/10 "2020-08-12T14:35:49Z")

</div>

Let us know if you have any further questions!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [August 27, 2020, 2:44pm UTC](https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008/11 "2020-08-27T14:44:28Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![matt.macadam](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/matt.macadam/32/55188_2.png) [@matt.macadam](https://community.auth0.com/u/matt.macadam)\
**Post date:** [May 17, 2021, 2:47pm UTC](https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008/12 "2021-05-17T14:47:05Z")

</div>

FYI, we have removed support for TLS 1.0/1.1 as of May 12, 2021. The above commands forcing TLS 1.0 and 1.1 will now return a handshake error regardless of tenant settings or SNI.

The request is rejected at the network edge so you won’t see any indication of the failure in tenant logs.

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [May 18, 2021, 9:43am UTC](https://community.auth0.com/t/tls-1-0-still-enabled-after-setting-tls-policy-to-recommended/47008/13 "2021-05-18T09:43:36Z")

</div>

Thanks for following up on that Matt!
