Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Deprecation of TLS 1.1 (900007)

Last Updated: 5/29/2020Categories: InformationalTotal Views: 1254Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

Starting with releases 2020.5 (hosted) and 9.3 (on-premises) NSX Lastline will disable support for TLS 1.1 to access the User Portal and APIs. All client applications that access NSX Lastline products will be required to support TLS 1.2. If you use clients that don’t support TLS 1.2 and above, please read the rationale and steps needed for continued operation below.

What is TLS?

Transport Layer Security (TLS) is a protocol that provides privacy and data integrity between two communicating applications. It is used by web browsers and other applications that require data to be securely exchanged over a network. There exist different versions of TLS: TLS 1.0, 1.1, 1.2 and 1.3.

What is the change?

NSX Lastline will disable the TLS 1.1 encryption protocol with the releases 2020.5 (hosted) and 9.3 (on-premises). This will prevent customers still using TLS 1.1 from accessing the User Portal and the APIs. (TLS 1.0 is already disabled.)

How will customers be impacted?

After NSX Lastline disables TLS 1.1, any inbound connections to the User Portal or the APIs that rely on TLS 1.1 will fail.

How can customers avoid a service disruption?

User Portal access

The User Portal is accessed using a browser: all browsers supported by the Portal already support TLS 1.2 and later by default. If you use an older browser (Internet Explorer older than version 11, Firefox older than version 27, Chrome older than version 38, Safari older than version 7), you will need to upgrade to a more recent (and supported) browser.

APIs access

APIs are accessed by issuing HTTPS requests via clients written in a variety of languages and libraries. The following languages/libraries are known to support TLS 1.2:

Python 2.7.9 and higher

Java 8 and higher

OpenSSL 1.0.1 and higher

Why are we implementing this change?

TLS 1.1 is an out-of-date protocol that does not support many newer and more secure cryptographic algorithms. TLS 1.2, which was introduced over a decade ago, fixes several security issues that have been identified in TLS 1.1. We have decided to make this change so that we can ensure the security of data in transit and stay up to date with modern security protocols and practices.

The change is consistent with best practices identified by the community. For example, the Internet Engineering Task Force is planning to deprecate the TLS 1.1 protocols; as of March 2020, all major browsers such as Google Chrome, Microsoft Internet Explorer, Apple Safari, and Mozilla Firefox flag TLS 1.1 connections as insecure.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Workspace ONE Boxer 21.06 for iOS での [タスク] ボタンおよびフォルダの廃止 (84470)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX Detonator

VMware NSX Defender

Related Versions:

Take Our Survey

Support Assistant