SecHub report results do not contain job UUID #864
Comments
de-jcup
added a commit
that referenced
this issue
Oct 29, 2021
- changed sereco product result transformer - does now set job uuid into reporting model (was missing) - changed existing pds integration test and check now for job uuid inside - added unit tests to check fallback handling - implemented fallback handling when no Job UUID in report JSON result (so old reports having no report job uuid inside will be repaired automatically)
de-jcup
added a commit
that referenced
this issue
Oct 29, 2021
Fix missing job uuid in report, closes #864
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Situation
With release
v0.27.0-serverthe reports did not conain a job uuid any longer.This is critical for sechub client interactive false-positive handling were the Job UUID of an report is used - and will fail because not existing.
Wanted
When user fetches reports the Job UUID must be in report again
Solution
Problem lays inside
SerecoProductResultTransformer.javawhere after the refactoring the job UUID was not set.This must be fixed.
Also
ScanSecHubReportshall have an fallback for reports that were currently already transformed without job uuid inside.The text was updated successfully, but these errors were encountered: