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
I recently had a scenario in my app where is required to use TLSv1.3 in my client-server communication.
I use SQL Management Studio 2022 in order to use TLSv1.3 and as client I use a java client. My problem is the following:
when I build the connection url in order to communicate with database even if I set the protocol to TLSv1.3 in my ClientHello I can see the both version of TLS is supported, TLSv1.2 and also TLSv1.3.
I already set the sslProtocol=TLSv1.3;encrypt=strict;trustServerCertificate=false; in my connection url.
Is any way to force the Client side to use the TLSv1.3 only?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, everyone,
I've the following scenario.
I recently had a scenario in my app where is required to use TLSv1.3 in my client-server communication.
I use SQL Management Studio 2022 in order to use TLSv1.3 and as client I use a java client. My problem is the following:
I already set the sslProtocol=TLSv1.3;encrypt=strict;trustServerCertificate=false; in my connection url.
Is any way to force the Client side to use the TLSv1.3 only?
Beta Was this translation helpful? Give feedback.
All reactions