Skip to content

Conversation

@mlitre
Copy link
Contributor

@mlitre mlitre commented May 15, 2025

Make sure we only send security events on failed connection attempts for invalid CPMS certificate. We also changed it so that we send invalid security event for the charge point certificate when the certificate signed response is not correct.

Describe your changes

We force or not the sending of certain events using the function parameters.

Issue ticket number and link

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • If OCPP 2.0.1 or OCPP2.1: I have updated the OCPP 2.x status document
  • I read the contribution documentation and made sure that my changes meet its requirements

@mlitre mlitre changed the title fix(ocpp16): Security events for invalide CP and CPMS certificates fix(ocpp16): Security events for invalid CP and CPMS certificates May 15, 2025
Make sure we only send security events on failed connection attempts for
invalid CPMS certificate. We also changed it so that we send invalid
security event for the charge point certificate when the certificate
signed response is not correct.

Signed-off-by: Martin Litre <[email protected]>
@mlitre mlitre force-pushed the fix/improve-sec-events-for-certs branch from 1d00d9e to 3018cdc Compare May 16, 2025 10:46
@mlitre mlitre merged commit 0cbb27a into main May 16, 2025
10 checks passed
@mlitre mlitre deleted the fix/improve-sec-events-for-certs branch May 16, 2025 11:28
Pietfried pushed a commit that referenced this pull request Nov 19, 2025
…1061) (#14)

Make sure we only send security events on failed connection attempts for
invalid CPMS certificate. We also changed it so that we send invalid
security event for the charge point certificate when the certificate
signed response is not correct.

Signed-off-by: Martin Litre <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants