Authentication (0x29) - Certificate-Based - UDS Diagnostics

Why Authentication 0x29 Replaces SecurityAccess 0x27

Aspect	SecurityAccess 0x27	Authentication 0x29
Cryptographic basis	Shared secret (symmetric)	PKI certificates (asymmetric ECDSA)
Key distribution	Same secret on all ECUs of same type → one breach = all ECUs compromised	ECU-unique certificate; compromise of one tool doesn't affect other ECUs
Revocation	No revocation mechanism	Certificate Revocation List (CRL) or OCSP for compromised tester certs
OEM adoption	Widely deployed (legacy)	Growing: AUTOSAR Adaptive, BMW/VW new platforms from ~2023
Standard	ISO 14229-1 Annex J	ISO 14229-1 Annex H (2020 edition)

0x29 Authentication Protocol Flow

0x29 Certificate-Based Mutual Authentication

  Step 1 — Request seed
  Tester → ECU:  0x29 0x01 0x02         (requestSeed; communicationType=asymmetric)
  ECU → Tester:  0x69 0x01 [serverChallenge][serverCertificate]
       │  ECU sends its certificate + random challenge for tester to sign

  Step 2 — Verify ECU certificate
  Tester verifies ECU cert chain → OEM Root CA
  Tester signs serverChallenge with tester private key

  Step 3 — Send key (tester credentials)
  Tester → ECU:  0x29 0x02 [testerCertificate][signedChallenge]
  ECU verifies tester cert → OEM tester CA
  ECU verifies signedChallenge using tester public key from cert
  ECU → Tester:  0x69 0x02 [ECU_SignedClientChallenge]
  Tester verifies ECU's signature → mutual authentication complete

  Step 4 — Authentication complete
  Tester → ECU:  0x29 0x03              (authenticationComplete)
  ECU → Tester:  0x69 0x03              (session unlocked for services)

  NRC 0x34: authenticationRequired (cert not yet verified)
  NRC 0x35: invalidKey (signature verification failed)

Certificate Chain Validation in DCM

Cdcm_auth.c

/* DCM 0x29 callback: validate tester certificate chain + signature */
#include "Dcm.h"
#include "CertMgmt.h"

Std_ReturnType Dcm_Auth_VerifyTesterCert(
    const uint8* testerCert,   uint32 testerCertLen,
    const uint8* signedChallenge, uint32 challengeLen,
    Dcm_NegativeResponseCodeType* ErrorCode)
{
    CertMgmt_VerifyResultType certResult;

    /* Step 1: Verify cert chain: tester cert → OEM Tester CA → OEM Root CA */
    certResult = CertMgmt_VerifyCertChain(
        testerCert, testerCertLen,
        CERTMGMT_SLOT_OEM_TESTER_CA,    /* intermediate CA in ECU protected storage */
        CERTMGMT_OTP_ROOT_CA_HASH       /* Root CA hash in OTP fuses */
    );
    if (certResult != CERTMGMT_VERIFY_OK) {
        *ErrorCode = DCM_E_INVALIDKEY;   /* NRC 0x35 */
        return E_NOT_OK;
    }

    /* Step 2: Verify tester signed the ECU's challenge correctly */
    certResult = CertMgmt_VerifySignature(
        g_serverChallenge, sizeof(g_serverChallenge),  /* challenge ECU generated */
        signedChallenge, challengeLen,
        testerCert, testerCertLen                      /* use tester pubkey from cert */
    );
    if (certResult != CERTMGMT_VERIFY_OK) {
        *ErrorCode = DCM_E_INVALIDKEY;
        return E_NOT_OK;
    }

    return E_OK;  /* authentication successful */
}

Summary

Authentication 0x29 shifts the security model from "secret shared with all ECUs of a type" (0x27) to "individual ECU certificate; tester has OEM-issued certificate". The key operational difference: if a tester's secret key (or algorithm) is leaked in 0x27, every ECU of that type is permanently compromised. In 0x29, a compromised tester certificate is revoked via CRL, and no other ECUs or testers are affected. AUTOSAR Adaptive platform ECUs are required to support 0x29; Classic platform adoption is increasing for high-security applications.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.