SignCertificate

Sends a certificate signing request so the CSMS can return a signed certificate.

Version: OCPP 2.0.1
Direction: Charge Point → CSMS
Functional block: Security

The station generates a key pair, keeps the private key, and sends the CSR here. The signed certificate comes back later in a CertificateSigned message, not in this response.

This is how a station rotates its own identity certificate without anyone visiting it.

Request

Field	Type	Required	Description
`csr`	string	Required	PEM-encoded certificate signing request.
`certificateType`	CertificateSigningUseEnumType	Optional	`ChargingStationCertificate` or `V2GCertificate`.

json

[2, "19223201", "SignCertificate", {
  "certificateType": "ChargingStationCertificate",
  "csr": "-----BEGIN CERTIFICATE REQUEST-----\nMIIB...\n-----END CERTIFICATE REQUEST-----"
}]

Response

Field	Type	Required	Description
`status`	GenericStatusEnumType	Required	`Accepted` or `Rejected`.
`statusInfo`	StatusInfoType	Optional	Reason code.

json

[3, "19223201", {
  "status": "Accepted"
}]

Implementation notes

`Accepted` means the CSR was received, not that a certificate exists. The certificate arrives in a subsequent CertificateSigned request from the CSMS.

A station whose certificate is close to expiry should start this well ahead of time — a failed rotation leaves it unable to connect at all.