[OCPP 1.6] InvalidCentralSystemCertificate being logged too frequently #1156
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ction 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. Signed-off-by: James Chapman <james.chapman@pionix.de>
james-ctc
requested review from
Pietfried,
hikinggrass and
mlitre
as code owners
mlitre
reviewed
Nov 26, 2025
mlitre
approved these changes
Dec 1, 2025
james-ctc
deleted the
fix/reduce-INVALIDCENTRALSYSTEMCERTIFICATE-logging
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Replaces PR #1155
Issue ticket number and link
Checklist before requesting a review