GetCertificateStatus
Asks the CSMS to check a certificate's revocation status via OCSP.
- Version
- OCPP 2.0.1
- Direction
- Charge Point → CSMS
- Functional block
- ISO 15118 Certificate Management
A charging station generally cannot reach an OCSP responder itself — it is on a private APN, or behind a firewall that permits only the CSMS. So it asks the CSMS to perform the check and hand back the signed OCSP response.
The station then passes that response to the vehicle as part of the 15118 exchange.
Request
| Field | Type | Required | Description |
|---|---|---|---|
ocspRequestData | OCSPRequestDataType | Required | Hash algorithm, issuer name and key hashes, serial number, and the responder URL. |
json
[2, "19223201", "GetCertificateStatus", {
"ocspRequestData": {
"hashAlgorithm": "SHA256",
"issuerNameHash": "3d8f...",
"issuerKeyHash": "9b21...",
"serialNumber": "0a1b2c3d",
"responderURL": "http://ocsp.example.com"
}
}]Response
| Field | Type | Required | Description |
|---|---|---|---|
status | GetCertificateStatusEnumType | Required | Accepted or Failed. |
ocspResult | string | Required | The DER-encoded OCSP response, base64-wrapped. |
statusInfo | StatusInfoType | Optional | Reason code. |
json
[3, "19223201", {
"status": "Accepted",
"ocspResult": "MIIBygoBAKCCAcMwggG..."
}]Implementation notes
`Accepted` means the check completed, not that the certificate is valid. The verdict is inside ocspResult, which the station forwards to the vehicle to evaluate.
A CSMS implementing this needs outbound access to the OCSP responders of every contract certificate authority it supports.