Forum Discussion
Manikanta_26608
Nimbostratus
NimbostratusHTTPS calls supporting TLS V 1.2
Hello,
I have a requirement that some of the applications with VIP's in F5 loadbalancer should support TLS 1.2. I thought of creating a SSL profile with cipher list as TLS V1_2. But i am not ver...
I don't think you need to do anything in particular to enable TLS1.2. It's one of the common features of the SSL/TLS handshake to pick the highest protocol version both parties support. Recent BigIP versions allow (and prefer) TLS1.2 to be used during client-side SSL handshake, unless you have disabled it yourself, or if your software version is badly outdated (10.2.2 and older). While TLS1.2 is given preference, there's nothing that by default would prevent your clients from falling back to older TLS versions if 1.2 is not supported.
- What is your BigIP verion? This SOL lists out the SSL/TLS versions which are enabled by the default clientssl profile configurations, or by the
Cipher String setting. https://support.f5.com/kb/en-us/solutions/public/13000/100/sol13156.htmlDEFAULT
- What is your BigIP verion? This SOL lists out the SSL/TLS versions which are enabled by the default clientssl profile configurations, or by the
Hannes_Rapp_162
Nacreous
NacreousI don't think you need to do anything in particular to enable TLS1.2. It's one of the common features of the SSL/TLS handshake to pick the highest protocol version both parties support. Recent BigIP versions allow (and prefer) TLS1.2 to be used during client-side SSL handshake, unless you have disabled it yourself, or if your software version is badly outdated (10.2.2 and older). While TLS1.2 is given preference, there's nothing that by default would prevent your clients from falling back to older TLS versions if 1.2 is not supported.
- What is your BigIP verion? This SOL lists out the SSL/TLS versions which are enabled by the default clientssl profile configurations, or by the
Cipher String setting. https://support.f5.com/kb/en-us/solutions/public/13000/100/sol13156.htmlDEFAULT
Manikanta_26608Thanks Hannes, It answers my question. My BigIP version is 11.5.3.So every call reaching Bigip should not support TLS 1.2. For the calls which supports TLS lower versions, lower ciphers will get picked up? How exactly this cipher selection works for each request.
- Hannes_Rapp_162
That's correct. If you have cURL calls which target the site using TLS1.0, these should work just fine. If your website is publicly accessible, you may validate your supported SSL/TLS versions using this SSL checker: https://www.ssllabs.com/ssltest/
- Manikanta_26608
That helps. The handshake simulations, protocols are clearly saying that my BigIP supports all TLS versions for all types of clients. I think it will be good for my requirement. Thank you.
- Manikanta_26608
Hi,
Currently we are using the default list of ciphers in SSL profile for 11.5.3 version. When a call comes and hit the VIP can you please tell me how it will prioritize the ciphers and select one cipher to process the request. can we have a list in prioritized format in the way they will be selected?
Thank you.
- Hannes_Rapp_162
@Manikanta -> https://support.f5.com/kb/en-us/solutions/public/15000/100/sol15194.html
Copy/Paste to BASH shell.
tmm --clientciphers 'DEFAULT' lists out all enabled cipher suites in the order of preference of your BigIP.