❗️

Disclaimer: OCPP is currently in beta release with firmware version 328. We strongly recommend using this beta release exclusively in test environments. Your feedback is greatly appreciated and will help us improve the final offering of OCPP. Other features of firmware version 328 can be used in production safely.

OCPP Security Profiles

Easee supports three OCPP security profiles, each offering different levels of security. Developers should choose the appropriate profile based on their security requirements and infrastructure capabilities.

Supported Profiles

Profile Details

Profile 0: Unsecured
Security Measures: None
Use Case: Development or testing environments only
Warning: Not recommended for production use

Charger <-----(Unsecured)-----> OCPP Server

Profile 1: Basic Authentication
Security Measures: HTTP Basic Authentication
Authentication: Yes
Encryption: No
Use Case: Environments where transport layer security is handled externally

Charger <-----(HTTP Basic Auth)-----> OCPP Server

Profile 2: TLS with Basic Authentication
Security Measures:
Transport Layer Security (TLS)
HTTP Basic Authentication
Authentication: Yes
Encryption: Yes
Use Case: Recommended for production environments

Charger <-----(TLS + HTTP Basic Auth)-----> OCPP Server

Implementation Notes

• Always use the highest security profile that your infrastructure supports.
• Profile 2 is strongly recommended for production deployments.
• Ensure proper certificate management when using Profile 2.