Skip to content
Documentation Menu

TC_074_CSMS — Update Charge Point Certificate by request of Central System

TC_074_CSMS — Update Charge Point Certificate by request of Central System

Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Central System, page 181.

Identification

FieldValue
Test case nameUpdate Charge Point Certificate by request of Central System
Test case IdTC_074_CSMS
System under testCentral System

Description

When SUT Charge Point, the tool shall take on the role of both Central System and Certificate Authority Server. Which means it will sign the certificate with its own certificate.

Purpose

To check if the Central System is able to request the Charge Point to renew its ChargePointCertificate.

Prerequisite(s)

The Central System supports security profile 3.

Before (Preparations)

Configuration State(s):

  • N/a

Memory State(s):

  • N/a

Reusable State(s):

  • N/a

Scenario Detail(s)

Charge Point (SUT)Central System (Tool)
2. The Charge Point responds with a ExtendedTriggerMessage.conf1. The Central System sends a ExtendedTriggerMessage.req
[The Charge Point generates a new public/private key pair and generates a Certificate Signing Request.]; 3. The Charge Point sends a SignCertificate.req.4. The Central System responds with a SignCertificate.conf.
[The Charge Point verifies the validity of the signed certificate.]; 6. The Charge Point responds with a CertificateSigned.conf.[Certificate Authority Server signs the certificate.]; 5. The Central System sends a CertificateSigned.req.
7. The Charge Point disconnects its current connection and reconnects to the Central System with the new certificate.8. The Central System accepts the incoming connection request using the new certificate.

Tool validation(s)

Charge Point side:

Step 2:

(Message: ExtendedTriggerMessage.conf) The status is Accepted

Step 6:

(Message: CertificateSigned.conf) The status is Accepted

Step 7:

The Charge Point reconnects to the Central System with the new certificate.

Central System side:

Step 1:

(Message: ExtendedTriggerMessage.req) The requestedMessage is SignChargePointCertificate The connectorId is <Omitted>

Step 4:

(Message: SignCertificate.conf) The status is Accepted

Step 5:

(Message: CertificateSigned.req) The certificateChain:

  • The certificateChain field contains valid PEM encoding.
  • The Public key of the client certificate matches the public key generated for the CSR at step 3.
  • The client certificate is signed using the configured security algorithm type.
  • The subject field commonName equals the configured serialNumber.
  • The public key of the client certificate adheres to the minimal OCPP key length requirements (RSA: 2048 / ECDSA: 224)

Expected result(s) / behaviour

Charge Point side:

  • N/a

Central System side:

The Charge Point and the Central System are connected.