TC_L_05_CS — Secure Firmware Update - InvalidCertificate
TC_L_05_CS — Secure Firmware Update - InvalidCertificate
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block L. FirmwareManagement, page 243.
Identification
| Field | Value |
|---|---|
| Test case name | Secure Firmware Update - InvalidCertificate |
| Test case Id | TC_L_05_CS |
| Use case Id(s) | L01 |
| Requirement(s) | L01.FR.01,L01.FR.02,L01.FR.10,L01.FR.20,L01.FR.21,L01.FR.22 |
| System under test | Charging Station |
| Functional block | L. FirmwareManagement |
Description
The CSMS is able to request the Charging Station to securely download and install a new firmware by sending an UpdateFirmwareRequest with a signingCertificate.
Purpose
To verify if the Charging Station is able to identify it receiving an invalid signing certificate and report this to the CSMS.
Prerequisite(s)
N/a
Before (Preparations)
Configuration State:
-
- <Configured Invalid Firmware SigningCertificate> should be a trusted certificate and not be the same as the <Configured Valid Firmware SigningCertificate>
Memory State:
- N/a
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 2. The Charging Station responds with a UpdateFirmwareResponse | 1. The OCTT sends a UpdateFirmwareRequest; with firmware.installDateTime <Current DateTime - 2 hours> firmware.location <Configured firmware_location> firmware.retrieveDateTime <Current DateTime - 2 hours> firmware.signingCertificate <Configured invalid firmware signingCertificate> firmware.signature <Configured signature> |
Tool validations
Step 2:
Message UpdateFirmwareResponse
- status InvalidCertificate OR RevokedCertificate
Post scenario validations
- N/a