PTV xServer internet will no longer be able to support TLS 1.1 or lower due to security updates in Azure. We informed you about this topic in the following blog post in April 2021.
PTV will start to deactivate the protocols with the upcoming map cluster updates.
Today the test systems of all our map clusters will support access with TLS 1.2 or higher only. We deactivated the access with TLS 1.1 or lower on all test environments for API Version 1 and API Version 2 alike.
Please test the access to the test system of your corresponding map cluster with your application and report any problem immediately.
The upcoming map updates for the map clusters will be announced as always via our PTV Developer Blog. You can subscribe to our blog to stay posted.
Next planned production updates with deactivation TLS 1.0 and 1.1:
08.03.2022 PTV World City Map Cluster (TomTom) with API version 1 (api-eu)
10.03.2022 PTV Europe City Map Cluster (TomTom) with API version 1 (eu-n)
22.03.2022 PTV America City Map Cluster with API version 1 (na-n)
26.04.2022 PTV World City Map Cluster with API version 2 (xserver2-eu)
28.04.2022 PTV World City Map Cluster with API version 2 (xserver2-us)
Your action is required if you are still using TLS 1.0 or 1.1 version, as the requests will not get through to our service after we updated the production environments of our map clusters.
- If you still use Java 7 runtime and lower or .NET Framework version 4.5 and lower your action is required.
- Update your framework to a newer version to guarantee access to our service after the update on our map clusters.
- PTV Java Clients
We recommend updating to a Java 8 runtime environment for the PTV xServer clients because Java 8 runtime supports TLS 1.2 by default. - .NET Framework
We recommend updating to NET 4.6 and above. You don’t need to do any additional work to support TLS 1.2, it’s supported by default. More detailed information regarding different NET. versions can be found here:
https://blogs.perficient.com/2016/04/28/tsl-1-2-and-net-support/
Additional hints to handle this topics can be found here:
https://stackoverflow.com/questions/34276358/how-to-test-which-version-of-tls-my-net-client-is-using
And here:
https://kevinchalet.com/2019/04/11/forcing-an-old-net-application-to-support-tls-1-2-without-recompiling-it/
Why do we do this: Microsoft announced the deactivation of Transport Layer Security 1.0 and 1.1.
Announcement from Microsoft on September 30th, 2020:
Transport Layer Security (TLS) 1.0 and 1.1 are security protocols for establishing encryption channels over computer networks. Microsoft has supported these protocols since Windows XP/Server 2003. However, due to evolving regulatory requirements as well as new security vulnerabilities in TLS 1.0, Microsoft recommends that customers remove TLS 1.0/1.1 dependencies in their environments and disable TLS 1.0 and 1.1 at the operating system level where possible. https://docs.microsoft.com/en-gb/lifecycle/announcements/transport-layer-security-1x-disablement
