InstallCertificate

CertificateManagement CSMS->CS OCPP 2.0.1

Sent by the CSMS to install a root CA certificate on the Charging Station for validating CSMS TLS certificates or V2G certificates.

Quick Reference

Required Fields

certificateType InstallCertificateUseEnumType

Type: V2GRootCertificate, MORootCertificate, CSMSRootCertificate, ManufacturerRootCertificate, V2GCertificateChain, OEMRootCertificate

certificate string(10000)

PEM-encoded certificate to install

Example Payload

{
  "certificateType": "CSMSRootCertificate",
  "certificate": "-----BEGIN CERTIFICATE-----\nMIICpDCCAYwCCQD...\n-----END CERTIFICATE-----"
}

Example Full Frame

[
  2,
  "msg-001",
  "InstallCertificate",
  {
    "certificateType": "CSMSRootCertificate",
    "certificate": "-----BEGIN CERTIFICATE-----\nMIICpDCCAYwCCQD...\n-----END CERTIFICATE-----"
  }
]

Format: [MessageType, MessageId, Action, Payload]

Open in Builder Go to Validator

Overview

InstallCertificate adds a trusted root CA certificate to the Charging Station’s trust store. This is required for the station to validate CSMS certificates or V2G-related certificates.

Expected Response

status: Accepted, Rejected, or Failed

Failed may indicate CertificateStoreMaxLengthExceeded (no space) or InvalidSignature.

Usage Notes

CSMSRootCertificate: The root CA the CSMS TLS certificate chains to
V2GRootCertificate: Root CA for ISO 15118 vehicle certificates
Each Charging Station has a finite certificate store — manage space carefully

Testing Tips

Install a CSMSRootCertificate and verify the station trusts the CSMS TLS connection
Test CertificateStoreMaxLengthExceeded by filling the certificate store

Common Errors

`TypeConstraintViolation`

Cause: certificateType uses an unsupported value

Solution: Use one of the supported InstallCertificateUseEnumType values

`GenericError`

Cause: Certificate storage is full

Solution: Charging Station responds with CertificateStoreMaxLengthExceeded - delete old certificates first