You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| CpoName | S |OCPP 1.6 security whitepaper edition 2 configuration key : not implemented yet|
129
-
| SecurityProfile | S |OCPP 1.6 security whitepaper edition 2 configuration key : not implemented yet|
126
+
| CertificateSignedMaxChainSize | S |None|
127
+
| CertificateStoreMaxLength |U|None|
128
+
| CpoName | S |None|
129
+
| SecurityProfile | S |None|
130
130
131
131
### OCPP security extensions
132
132
@@ -154,6 +154,8 @@ In Charge Point role, it can optionnaly handle the storage of the security event
154
154
155
155
In Charge Point role, the user application can generate custom security events and defines its criticity so that they are forwarded to the Central System.
156
156
157
+
In Charge Point role, the notification of security events can be enabled or disabled with the IChargePointConfig::securityEventNotificationEnabled() configuration. This can be usefull to disable them when the Central System does not implement the security extensions.
158
+
157
159
#### Extended trigger messages
158
160
159
161
**Open OCPP** support this feature for both Charge Point and Central System roles.
0 commit comments