You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
I'm running the zap-cli active scan in the OWASP zap docker container. The zap scan took more than 3 hour / a day due to the authentication URL in our authentication script is inaccessible in the Jenkins environment but the issue is already solved.
Due to the longer time, the ZAP scan causes the lower memory of the Jenkins.
We were thinking to add a timed out in our tests. Is it possible to add a timed out when running the zap active scan in zap-cli?
The text was updated successfully, but these errors were encountered:
Hi!
I'm running the zap-cli active scan in the OWASP zap docker container. The zap scan took more than 3 hour / a day due to the authentication URL in our authentication script is inaccessible in the Jenkins environment but the issue is already solved.
Due to the longer time, the ZAP scan causes the lower memory of the Jenkins.
We were thinking to add a timed out in our tests. Is it possible to add a timed out when running the zap active scan in zap-cli?
The text was updated successfully, but these errors were encountered: