Certificate Provisioning for OCPP
Every charger communicates with its charge point management system (CPMS) over the Open Charge Point Protocol (OCPP) to start sessions, send meter values and receive updates. Hubject OCPP PKI is a managed public key infrastructure (PKI) service that issues and renews the X.509 certificates this connection requires under OCPP Security Profiles 2 and 3. Chargers and backend exchange data over an encrypted, authenticated connection, while Hubject operates the certificate authority.

Benefits
How it works
From onboarding to encrypted charger-to-backend connections in five steps.
Complete onboarding
Contact Hubject to begin the one-time onboarding process, which includes an audit and integration with the Hubject OCPP PKI REST API.
Request certificates
Request a server certificate for each CPMS backend endpoint and, for mutual TLS (mTLS), a client certificate for each charger.
Hubject issues the certificates
The certificates are issued from the Hubject OCPP Sub-CA, which is chained to the Hubject OCPP Root CA.
Install certificates
Install the certificates on the backend and on each charger. OCPP 2.0.1 and OCPP 2.1 include standard messages for installing certificates.
Establish secure connections
Chargers and backend connect over an encrypted TLS connection, with mutual authentication under Security Profile 3. Certificates are renewed through Hubject before they expire, ensuring continuous protection.
Features
Hubject OCPP PKI is designed specifically for eMobility and OCPP. Hubject also operates the ISO 15118 Plug&Charge PKI, which is trusted across the eMobility ecosystem.
Server and client certificates
TLS server certificates for CPMS backend endpoints enable the backend to prove its identity to every charger under Security Profile 2.
TLS client certificates, one per charger, enable each charger to prove its identity to the backend through mTLS under Security Profile 3.
A certificate hierarchy operated by Hubject
The Hubject OCPP Root CA and a dedicated OCPP Sub-CA are both operated by Hubject.
All server and client certificates chain to a single trusted root.
Certificates use the ECDSA P-384 algorithm.
Compatibility across OCPP versions
Certificates are compatible with OCPP 1.6 (with the OCPP Security Whitepaper), OCPP 2.0.1 and OCPP 2.1.
Security Profiles 2 and 3 are available in all three versions.
OCPP 2.0.1 and OCPP 2.1 include standard messages for installing and renewing certificates.
Who it is for
Pricing
Pricing consists of a one-time onboarding fee and an annual price per certificate. The price per certificate decreases as annual volume increases.
Annual price per certificate
Available worldwide
Hubject OCPP PKI is available worldwide. It is delivered through a REST API, following an audit and one-time onboarding.

Secure your OCPP connections
Contact Hubject to begin onboarding and request your first certificates.



