Added support to report and consume security events in OCPP1.6 #182
Conversation
|
@Pietfried there is no checking for ciritical security events. The Charge Point SHALL inform the Central System of the security events by sending a SecurityEventNotification.req, to the Central System. We dont have to send them all. I have added this to the 2.0.1 implementation. Another boolean to the internal function. |
@RobertDeLeeuw I checked the spec and you are correct that only critical security events shall be sent. Still OCTT1.6 tests for SecurityEventRequests being sent like InvalidChargePointCertificate (which is not critical). I would propably go with just sending all of them, as this is not specifically prohibited in the spec as far as I can see. What do you think? |
Pietfried
force-pushed
the
pg-ocpp-external-security-event
branch
2 times, most recently
from
6996550
to
e8f0122
Compare
* now treating SecurityEventNotification like transaction-related message * Revert SecurityEvent enum back to strings Signed-off-by: Kai-Uwe Hermann <[email protected]> Signed-off-by: pietfried <[email protected]>
Pietfried
force-pushed
the
pg-ocpp-external-security-event
branch
from
e8f0122
to
3c685f7
Compare
No description provided.