Skip to content

🐛 Bug: Unvalidated Constraint Cases in OCPP Specification-Based Testing Tool Report #379

@jongchan988

Description

@jongchan988

📜 Description

Hello,

We are currently conducting research on the OCPP protocol and would like to share some of our findings.
In our OCPP specification-based testing tool, we observed cases where the resulting constraints are not being validated.
Even if it takes some time to fix, we kindly ask that you leave a comment to acknowledge that the issue has been recognized.

OCPP Go Report.xlsx

Thank you for your attention and support.
Best regards,

👟 Reproduction steps

read file please

👍 Expected behavior

read file please

👎 Actual Behavior

read file please

What OCPP version are you using?

  • OCPP 1.6
  • OCPP 2.0.1

Are you using any OCPP extensions?

  • OCPP 1.6 Security
  • OCPP 1.6 Plug and Charge

release version

No response

📃 Provide any additional context for the Bug.

No response

👀 Have you spent some time to check if this bug has been found before?

  • I checked and didn't find a similar issue

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions