-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Alert.xml missing code 30002 #2995
Comments
Thats not an error reported by ZAP, so it could be a Sonar issue. |
It's being used by scanner Format String Error. |
Hmm, looking at the alert.xml it definitely is in the header comment but this is the last one as xml definition: |
Ok, so I failed a grepping :P |
To be honest I'm not too familiar with zaproxy and zaproxy-sonar co-operation to say if that description is essential. Just figured out 1+1 when the warning was there and that description was missing. I assumed that Sonar is getting description of the issue from there. |
It could well be :) |
Oh, quick question - how are you integrating ZAP in Sonar? or ?? |
Jenkins is running the analyze and storing results to a file using plugin https://wiki.jenkins-ci.org/display/JENKINS/ZAProxy+Plugin. Sonar picks up the file using plugin https://github.com/stevespringett/zap-sonar-plugin |
It seems the Sonar plugin uses other file: Worth trying with a custom file that has the missing plugin: |
Thank you for your support! I modifed rules.xml in sonar-zap-plugin adding description for 30002, compiled and installed it. Now the warning is gone. I'll let sonar-zap-plugin project to know this issue |
Great! Thanks for letting us know. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
When running Sonar after ZAProxy run there is a warning:
WARNING] The rule ZAProxy:30002 doesn't exist.
There is discussion over this alert in another issue #1558 but probably maintaining alerts has been forgotten since the last alert currently is 30001.
The text was updated successfully, but these errors were encountered: