TC_076_CSMS — Delete a specific certificate from the Charge Point

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

Identification

Field	Value
Test case name	Delete a specific certificate from the Charge Point
Test case Id	TC_076_CSMS
System under test	Central System

Description

To facilitate the management of the Charge Point’s installed certificates, a method of deleting an installed certificate is provided. The Central System requests the Charge Point to delete a specific certificate.

Purpose

To check if the Central System is able to delete an installed certificate from the Charge Point.

Prerequisite(s)

Before (Preparations)

Configuration State(s):

Memory State(s):

Reusable State(s):

Scenario Detail(s)

Charge Point (SUT)	Central System (Tool)
The OCTT requests the Central System to install CentralSystemRootCertificate 2
2. The Charge Point responds with a InstallCertificate.conf	1. The Central System sends a InstallCertificate.req
The OCTT requests the Central System to delete the just installed CentralSystemRootCertificate 2
4. The Charge Point responds with a GetInstalledCertificateIds.conf	3. The Central System sends a GetInstalledCertificateIds.req; Note(s): The Central System sends a GetInstalledCertificateIds.req to confirm the hashAlgorithm it needs to use for requesting the deletion of the Root certificate.
6. The Charge Point responds with a DeleteCertificate.conf	5. The Central System sends a DeleteCertificate.req
8. The Charge Point responds with a GetInstalledCertificateIds.conf	7. The Central System optionally sends a GetInstalledCertificateIds.req; Note(s): This step is optional. It is only used for the Central System to confirm the Root certificate actually has been deleted.
Note(s):; - Steps 1 - 8 will be repeated for each hash algorithm (SHA256, SHA384, SHA512).

Tool validation(s)

Charge Point side:

Step 4:

(Message: GetInstalledCertificateIds.conf) status is Accepted certificateHashData.hashAlgorithm is <For each hash algorithm; (SHA256, SHA384, SHA512)>

Step 6:

(Message: DeleteCertificate.conf) status is Accepted

Central System side:

Step 5:

(Message: DeleteCertificate.req) hashAlgorithm is <Configured HashAlgorithm> (It needs to be equal to the hashAlgorithm returned at step 4) certificateHashData is <Includes the certificate information of the installed CentralSystemRootCertificate.> The individual fields of the certificateHashData are verified by the OCTT (the OCTT compares these with its own certificateHashData calculation).

Expected result(s) / behaviour

Charge Point side:

Central System side: