Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EvseV2G: always assign GenChallenge and EVSETimeStamp in PaymentDetailsRes #533

Merged

Conversation

barsnick
Copy link
Contributor

@barsnick barsnick commented Feb 7, 2024

When responding in PaymentDetailsRes with a FAILED ResponseCode, EVSETimeStamp and GenChallenge need to be assigned, even if unused. Especially GenChallenge needs to conform to the fixed size mandated by the schema.

Previously, GenChallenge was sent with size 0 in this case, which could lead to message validation errors on the receiving EV side.

Signed-off-by: Moritz Barsnick [email protected]

…lsRes

When responding in PaymentDetailsRes with a FAILED ResponseCode,
EVSETimeStamp and GenChallenge need to be assigned, even if unused.
Especially GenChallenge needs to conform to the fixed size mandated by the
schema.

Previously, GenChallenge was sent with size 0 in this case, which could lead
to message validation errors on the receiving EV side.

Signed-off-by: Moritz Barsnick <[email protected]>
@barsnick barsnick added the bug Something isn't working label Feb 7, 2024
Copy link
Contributor

@SebaLukas SebaLukas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@SebaLukas SebaLukas merged commit 99b066a into EVerest:main Feb 8, 2024
5 checks passed
@barsnick barsnick deleted the cb-evsev2g-fix-paymentdetailsres branch February 8, 2024 07:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants