TC_077_CS — Invalid ChargePointCertificate Security Event
TC_077_CS — Invalid ChargePointCertificate Security Event
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 100.
Identification
| Field | Value |
|---|---|
| Test case name | Invalid ChargePointCertificate Security Event |
| Test case Id | TC_077_CS |
| System under test | Charge Point |
Description
The Charge Point notifies the Central System of an invalid certificate. The tool shall take on the role of both Central System and Certificate Authority Server. Which means it will sign the certificate using its own certificate.
Purpose
To check if the Charge Point is able to register a security event and is able not notify the Central System about it.
Prerequisite(s)
The Charge Point supports security profile 3.
Before (Preparations)
Configuration State(s):
- CpoName is <The configured Vendor Name>.
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.conf | 1. 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. | 5. The Central System sends a CertificateSigned.req. |
| 7. The Charge Point sends a SecurityEventNotification.req | 8. The Central System responds with a SecurityEventNotification.conf |
Tool validation(s)
Charge Point side:
Step 2:
(Message: ExtendedTriggerMessage.conf) The status is Accepted
Step 6:
(Message: CertificateSigned.conf) The status is Rejected
Step 7:
(Message: SecurityEventNotification.req) The type is InvalidChargePointCertificate
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 certificate is <An invalid certificate>
Expected result(s) / behaviour
Charge Point side:
- N/a
Central System side:
- N/a