TC_A_14_CS — Update Charging Station Certificate by request of CSMS - Invalid certificate
TC_A_14_CS — Update Charging Station Certificate by request of CSMS - Invalid certificate
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block A. Security, page 18.
Identification
| Field | Value |
|---|---|
| Test case name | Update Charging Station Certificate by request of CSMS - Invalid certificate |
| Test case Id | TC_A_14_CS |
| Use case Id(s) | A02 |
| Requirement(s) | A02.FR.07,A03.FR.07 |
| System under test | Charging Station |
| Functional block | A. Security |
Description
The CSMS is able to request the Charging Station to update its charging station certificate using the TriggerMessageRequest message.
Purpose
To verify if the Charging Station is able to discard an invalid certificate and report a security event.
Prerequisite(s)
- The Charging Station supports security profile 3
- The active NetworkConnectionProfile uses security profile 3.
Before (Preparations)
Configuration State:
- N/a
Memory State:
- N/a
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 2. The Charging Station responds with a TriggerMessageResponse | 1. The OCTT sends a TriggerMessageRequest; With requestedMessage SignChargingStationCertificate |
| 3 The Charging Station sends a SignCertificateRequest | 4. The OCTT responds with a SignCertificateResponse; With status Accepted |
| 6. The Charging Station responds with a CertificateSignedResponse | 5. The OCTT sends a CertificateSignedRequest; With certificateChain <Configured invalid_signingCertificate> certificateType ChargingStationCertificate |
| 7 The Charging Station sends a SecurityEventNotificationRequest | 8 The OCTT responds with a SecurityEventNotificationResponse |
Tool validations
Step 2:
Message: TriggerMessageResponse
- status must be Accepted
Step 3:
Message: SignCertificateRequest
- csr must contain <An CSR that meets the following requirements: When using RSA or DSA the key must be at least 2048 bits long. and when using elliptic curve cryptography the key must be at least 224 bits long. The received CSR must be transmitted as described in RFC 2986 and then encoded in Privacy-Enhanced Mail (PEM) format.>
Step 6:
Message: CertificateSignedResponse
- status must be Rejected
Step 7:
Message: SecurityEventNotificationRequest
- type must be InvalidChargingStationCertificate
Post scenario validations
- N/a