Skip to content

Conversation

@james-ctc
Copy link
Member

Describe your changes

fix: InvalidCentralSystemCertificate was logged on every failed connection

A CSMS certificate may be considered invalid when a charger has the incorrect time. This can be recovered by using NTP. However a security event is raised for each failed connection attempt until the correct time is set.

This change ensures that InvalidCentralSystemCertificate is logged only on the first occurance.

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

@florinmihut florinmihut force-pushed the fix/reduce-INVALIDCENTRALSYSTEMCERTIFICATE-logging branch from a4a7514 to 39b8a33 Compare November 25, 2025 16:11
@felix-ulonska
Copy link

⚠️ PR Affected by Security Incident

This PR was affected by a security incident where a compromised account force-pushed to this branch and closed the PR.

✅ Branch History Restored

We've run an automation that restored the complete history of this branch to the time before the attack. All your commits are preserved. Nothing has been updated in the respective branch in case someone force-pushed after the attack but before our automation.

🔄 Action Required

GitHub won't allow reopening this PR after the close and force-push. Please:

  • Open a new PR from your branch to the target branch. You can use the following link to open a new PR: Open PR
  • Link back to this PR in the description to include previous discussions

We apologize for the inconvenience.

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.

5 participants