Skip to content
Documentation Menu

TC_M_20_CSMS — Delete a certificate from a Charging Station - Success

TC_M_20_CSMS — Delete a certificate from a Charging Station - Success

Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block M. ISO 15118 CertificateManagement, page 467.

Identification

FieldValue
Test case nameDelete a certificate from a Charging Station - Success
Test case IdTC_M_20_CSMS
Use case Id(s)M04
Requirement(s)M04.FR.01,M04.FR.07
System under testCSMS
Functional blockM. ISO 15118 CertificateManagement

Description

The CSMS is able to request the Charging Station to delete an installed certificate using the DeleteCertificateRequest message, using all available hash algorithms, including SHA256, SHA384, and SHA512.

Purpose

To verify if CSMS is able to request a Charging Station to delete an installed certificate, using all available hash algorithms, including SHA256, SHA384, and SHA512.

Prerequisite(s)

N/a

Before (Preparations)

Configuration State:

  • N/a

Memory State:

  • N/a

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
1. CertificateInstalled with certificateType CSMSRootCertificate.
Manual Action: Request the CSMS to send a DeleteCertificateRequest.
3. The OCTT responds with a GetInstalledCertificateIdsResponse; With status is Accepted certificateHashDataChain contains an entry with following values: certificateHashDataChain[0].certificateType is CSMSRootCertificate certificateHashDataChain[0].certificateHashData.ha shAlgorithm is SHA2562. The CSMS sends a GetInstalledCertificateIdsRequest
5. The OCTT responds with a DeleteCertificateResponse; With status is Accepted4. The CSMS sends a DeleteCertificateRequest
Note(s):; - Steps 1 - 5 will be repeated for each hash algorithm (SHA256, SHA384, SHA512).

Tool validations

Step 2:

Message: GetInstalledCertificateIdsRequest

  • certificateType contains CSMSRootCertificate OR is omitted.

Step 4:

Message: DeleteCertificateRequest

  • certificateHashData is <Returned certificateHashData at Step 3>.

Post scenario validations

  • N/a