Certificate Signed

Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.4 (Messages); Use Cases A02 — Update Charging Station Certificate by request of CSMS, A03 — Update Charging Station Certificate initiated by the Charging Station (Functional Block A. Security)

Overview

The CSMS sends CertificateSignedRequest to deliver a signed PEM-encoded X.509 certificate (with sub-CA chain when applicable) to the Charging Station. The certificate is the result of the CSR previously sent by the CS in SignCertificateRequest.

The optional certificateType indicates whether the signed certificate is for the CS-to-CSMS TLS connection, the 15118 / V2G connection, or both. It is required when the originating SignCertificateRequest contained a certificateType AND both connections are implemented.

The maximum size of certificateChain is configurable via MaxCertificateChainSize.

Sequence Diagram

CSMS  ──── CertificateSignedRequest ────▶  Charging Station
            (certificateChain, certificateType?)
                                           Verify validity, switch when valid
CSMS  ◀─── CertificateSignedResponse ────  Charging Station
            (status, statusInfo?)

Initiator

CSMS → Charging Station

Fields

CertificateSignedStatusEnumType values

Accepted, Rejected.

Examples

{
  "certificateChain": "-----BEGIN CERTIFICATE-----\nMIID...\n-----END CERTIFICATE-----\n-----BEGIN CERTIFICATE-----\nMIIE...\n-----END CERTIFICATE-----",
  "certificateType": "ChargingStationCertificate"
}

{
  "status": "Accepted"
}

Schema

Source: schemas/CertificateSignedRequest.json, schemas/CertificateSignedResponse.json (OCPP 2.0.1 FINAL)