Reports are not generated unless autooff is used
See original GitHub issueDescribe the bug
With the latest release of the docker image, the baseline scan does not generate the reports unless the --autooff
flag is used.
I believe this is related to the Baseline scan changes previously announced, although they shouldn’t have caused any issues with the reports.
I checked the source code as suggested, but I can’t see why the reports should not be generated.
To Reproduce Steps to reproduce the behavior:
- Run
docker run --name owasp -v $(pwd)/test-zap:/zap/wrk:rw --rm -i -t owasp/zap2docker-stable zap-baseline.py -t https://start.spring.io -d -r report.html -J report.json
=> No report is generated in the mounted folder - Run
docker run --name owasp -v $(pwd)/test-zap:/zap/wrk:rw --rm -i -t owasp/zap2docker-stable zap-baseline.py -t https://start.spring.io -d -r report.html -J report.json --autooff
=> Reports are successfully generated
Expected behavior
Two reports should be generated in the mounted folder. One in JSON format, the other in HTML format , even when not using the --autooff
flag
Software versions
Using ZAP inside of the owasp/zap2docker-stable
docker image.
SHA: owasp/zap2docker-stable@sha256:461cfec7f6ce3c6ce7a8aceef773ed482d6ee572a16f1e6e86bd78799ae483cf
Would you like to help fix this issue? No
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top GitHub Comments
We think we know whats going on and hope to have a work around asap. And then a proper fix once we’ve had a chance to test it thoroughly…
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.