VDA EDI Tools

OFTP2 TLS 1.3 Migration Checklist for Automotive Suppliers (2026–2027)

VDA EDI Tools Blog · 2026-11-14

If your company exchanges VDA messages with German OEMs or Tier-1s, the files almost certainly travel over OFTP2 - the Odette File Transfer Protocol. And if you have not touched your OFTP2 configuration in a few years, 2026 is the year you must: the industry's security profile for OFTP2 is being tightened, and the deadlines are no longer advisory.

What changed, and who decided it

Two documents define what a compliant OFTP2 setup looks like, and both were updated in March 2026:

On top of these, the Odette OFTP2 Experts Group has publicly announced two hardening measures: TLS 1.0 is declared obsolete and will move to unsupported once vendors have migrated their TLS libraries, and the minimum certificate key length is being raised to 3072 bits to align with current cybersecurity guidance. In Germany, the VDA side of the house tracks the same transition through VDA 4933 Teil 1, the application recommendation for OFTP2 in the automotive industry. Software vendors are shipping compliant releases throughout 2026, and the working assumption across the German automotive EDI community - reinforced by vendor guidance published as recently as November 2026 - is that TLS 1.3 (RFC 8446) becomes mandatory from 1 January 2027, with many OEM test environments enforcing it earlier. Do not wait for a formal letter: treat 2027-01-01 as your cutover date and work backwards.

What actually changes on the wire

The OFTP2 protocol itself (RFC 5024) is unchanged - the SFID, SFPA/SFPU session commands, credit windows, EERP/NERP end responses all stay. What changes is the security envelope around the session and the files:

The checklist, deadline by deadline

Now – 2026-11-30: inventory and certificates

  1. List every OFTP2 endpoint: your own server, your EDI provider's managed service, and every direct partner connection. For each, record software product and version, current TLS version, certificate subject, issuer, key length and expiry date.
  2. Confirm with your software vendor that your release supports TLS 1.3 with the three compliant cipher suites and the new CMS algorithms. If you run an older on-premise installation, plan the upgrade first - everything else depends on it.
  3. Order new 3072-bit certificates from a CA that your key OEMs accept, and map each certificate to the Odette ID it authenticates.

2026-12-01 – 2026-12-15: configure staging

  1. In a test environment, enable TLS 1.3, disable TLS 1.0/1.1, install the new certificates, and tighten SSP/SRP to reject SHA-1.
  2. Verify signed EERP (end-to-end response) flows still work - partners depend on these receipts for their audit trail, and they are easy to break when certificate chains change.
  3. Document the rollback: keep the old profile active on a separate port until partner migration is complete.

2026-12-16 – 2026-12-31: interoperability testing

  1. Run test exchanges with every trading partner against the OP09 v3.3 test-case logic: session establishment with mutual authentication, encrypted and signed file transfer, restart after interruption, and EERP/NERP handling.
  2. Confirm with each partner which side initiates and on which schedule - OFTP2 is polling-based, and firewall pinholes, DNS names and port 3305 (or your agreed port) must all be re-validated after the TLS profile change.
  3. Capture evidence: logs, certificate fingerprints, timestamps. You will need them for your OEM's security questionnaire.

2027-01-01 onwards: production

  1. Cut over partner by partner, not all at once. Keep monitoring failed session attempts daily for the first two weeks - a TLS handshake failure looks identical to "partner offline" in many dashboards.
  2. Exception handling: very small partners without in-house OFTP2 expertise are typically routed through a Tier-1 or provider-operated gateway. If that is you, ask your customer now, not in January.

The pitfall nobody budgets for: message content

A perfect TLS 1.3 channel does nothing for the content travelling over it. Every migration window is also when partners re-test their VDA 4984 DELFOR and VDA 4987 DESADV mappings - and a channel that finally works tends to surface content errors that were previously hidden by transfer failures. Before your first production file goes out, validate the payload: paste your DELFOR into the VDA 4984 validator and your despatch advice into the VDA 4987 validator - both run entirely in your browser, so test files containing real part numbers and volumes never leave your machine. Fix the envelope, segment counts and date formats there first, then send. The combination "new TLS profile + clean message + passing interoperability test" is what gets you through the gate in January without emergency weekend calls.

Update (2026-11-14): the countdown edition is live - OFTP2 TLS 1.3 Upgrade Checklist: 48 Days Until the 2027 Deadline, with the per-OEM certificate CA whitelist and Odette Conformance Tool test steps.

Try it: Once your OFTP2 channel is solid, validate the message content itself - paste a DELFOR or DESADV file and check it locally in your browser. Open the tool →

← All articles