PTV xServer internet – PTV America City Map cluster Here with API Version 1 – deactivation of TLS 1.0 and 1.1

We would like to inform you that we plan to deactivate TLS 1.0 and 1.1 on the PTV America City Map [Here] production cluster with API Version 1 on March 22nd , 2022.

The following tasks will be completed in the scope of this maintenance:

  • Deactivation of Transport Layer Security (TLS) 1.0 and 1.1
  • Map update to PTV America City Map 2022.2H

The deactivation of TLS 1.0 and 1.1 is a major change that may have effect on your application.

More details regarding this topic can be found on our Developer Blog post about deactivation of TLS 1.0 and 1.1.

Please test your application on the already updated test system and report any problem immediately.  

PTV xServer internet – PTV Europe and World City Map cluster TomTom with API Version 1 – deactivation of TLS 1.0 and 1.1

We would like to inform you that we plan to deactivate TLS 1.0 and 1.1 on the PTV World and Europe City Map [TomTom] production cluster with API Version 1 on March 8th and 10th, 2022.

The following tasks will be completed in the scope of this maintenance:

March 8th, 2022:   PTV World City Map [TomTom] production

  • Deactivation of Transport Layer Security (TLS) 1.0 and 1.1
  • Map update to PTV World City Map 2022.1T
  • PTV xServer update to newest xServer API version 1

March 10th, 2022:  PTV Europe City Map [TomTom] production

  • Deactivation of Transport Layer Security (TLS) 1.0 and 1.1

The deactivation of TLS 1.0 and 1.1 is a major change that may have effect on your application.
More details regarding this topic can be found on our Developer Blog post about deactivation of TLS 1.0 and 1.1.

Please test your application on the already updated test system and report any problem immediately.  

Deactivation of Transport Layer Security (TLS) 1.0 and 1.1 starts today!

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.

  1. If you still use Java 7 runtime and lower or .NET Framework version 4.5 and lower your action is required.
  2. Update your framework to a newer version to guarantee access to our service after the update on our map clusters.

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

Critical vulnerability in Log4j

The latest update to this post is available here!

On Friday 09.12.21 a critical vulnerability (Log4Shell) in the widely used Java library Log4j has been identified. According to the assessment of many authorities, this leads to an extremely critical threat situation, which is why, among others, the Federal Office for Information Security (BSI) in Germany has upgraded its existing cyber security warning to warning level red (see Common Vulnerabilities and Exposures and BSI).

The affected component is also used in some PTV products. This affects both customer installations and the cloud offering of PTV Group.

Overview

List of products (affected, but patched)

  • PTV xServer internet 1 / PTV xServer internet 2
  • PTV TLN planner internet
  • PTV Route Optimizer SaaS / Demonstrator
  • PTV Developer
  • PTV Visum Publisher

List of products (affected)

  • PTV xServer 2.x (on prem)
  • PTV xServer 1.34 (on prem)
  • PTV MaaS Modeller

List of products (possibly affected)

  • PTV Route Optimiser CL
  • PTV Route Optimiser ST
  • PTV Map&Market
  • PTV Arrival Board / Trip Creator / EM Portal
  • PTV Drive&Arrive

List of products (not affected)

  • PTV xServer < 1.34 (on prem)
  • PTV Road Editor
  • PTV Map&Guide internet
  • PTV Map&Guide intranet
  • PTV Navigator Licence Manager
  • PTV Navigator App
  • PTV Drive&Arrive App
  • PTV Visum
  • PTV Vissim
  • PTV Vistro
  • PTV Viswalk
  • PTV Balance and PTV Epics
  • PTV Hyperpath
  • PTV TRE and PTV Tre-Addin
  • PTV Optima

We have therefore been working on updating the affected PTV products since the vulnerability was announced.

For the vulnerability, there is already a security update from the manufacturer with version Log4j 2.15.0. In addition, all products that use Log4j – including all affected PTV Products – must be adapted.

For cloud products, the update will be performed by PTV in its own data centers.

For customer-owned installations, we will provide an update in the short term and offer it for download. All customers will receive direct information about this in a timely manner.

Concerning further technical questions, please contact your Product Support.

PTV xServer internet technical information – Reported issues for PTV Europe City Map [TomTom] with API Version 1

On September 1st 2021 we did the update on the PTV Europe City Map [TomTom] with API Version 1. After the switch to production some customers had problems.

Here are the issues reported and the corresponding solution:

  • There was a report that a customer could no longer connect to the service. After an analysis we found out that he used the IP address instead of URL.
    Please have in mind that we don´t guarantee the stability of our IP addresses, so please only use the URLs to address our service.

  • There was an issue with an error of dataCompatibilityVersion does not match.
    After the analysis of the issue we found out that the error message was misleading. Instead of data compatibility it is a profile schema validation error.

    In our documentation we note that the schema validation for the profile snippet should only be used for development or debugging issues, because of the performance. It is not meant for productive usage, nevertheless it should work like intended.

    Do not use http://localhost:500×0 as schema url since this internal url might or will not work. We documented in our manual that we support the following notation for the schema location:

    <Profile xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:noNamespaceSchemaLocation=

      "../../schema/XRouteProfile.xsd">

      <Common language="de" coordinateFormat="PTV_GEODECIMAL" majorVersion="1" minorVersion="0"/>

    </Profile>

    What also works is the notation like specified in our RawRequestRunner samples:

    <Profile xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:noNamespaceSchemaLocation=\http:///xroute/schema/XRouteProfile.xsd\>   

    We see that is a minor change if you used that differently before. Nevertheless, this is the documented and supported way and should be used accordingly.

 

We kindly ask you to please always test your application on the provided test system and report any problem immediately.

PTV xServer internet update – PTV Europe City Map [HERE] with API Version 1

We did perform technical maintenance today that did not require any downtime.
The following tasks were completed in the scope of this maintenance.

PTV Europe City Map [HERE] – TEST and INTEGRATION – cluster with API version 1:

  • Operating system change from Windows Server to Ubuntu Linux

Please test your application on the today updated test system and report any problem immediately.