-
Notifications
You must be signed in to change notification settings - Fork 4
Develop: Zap stays in Scanner #26
Comments
Hi Timo, you LOG file indicates that your ZAP Spider returns no URLs, in this case the ZAP Scanner complains that its not able to scan... ** 2018-11-16 12:50:00.561 INFO 118 --- [pool-1-thread-4] i.s.zap.service.zap.ZapService : Recalling 0 requests to zap.** 214949 [ZAP-ProxyThread-78] WARN org.zaproxy.zap.extension.api.API - Bad request to API endpoint [/xml/ascan/action/scan/] from [127.0.0.1]: Have you tried to scan your service (http://10.10.11.104:3000/) local with ZAP first, to test your configuration you would like to automate? Maybe the KR |
Hi Robert, I tried it now with:
In all cases, I get the same error. I updated the title, as it stays in scanner, saying the task spider is complete. Cheers, |
I guess due to the error message, that the targetUrl is not in the siteTree and the source of the error is here: |
Hi Timo |
First test: With the current development version and a local build it works. More tests tomorrow. |
Using latest securecodebox/engine:develop and securecodebox/zap:develop (using docker-compose pull) results in an error on the engine. Used versions: Logs:
With the self build of the current master of github it works. By using develop branch of engine, it is not working. Maybe I am forced to use the new api (which is hard without documentation)? |
The last problem doesn't has to be a problem with zap. |
Does this error crash the container? Also the current develop state is already relatively well documented, the only thing missing is the generated markdown rest api documentation. But you can always access the dynamic swagger page of the engine. (located at |
no |
I am using docker-compose.yml with a self build engine and zap. Both are current develop-branch without modifications.
I scan the juice shop via swagger:
[ { "name": "ZAP Scan 10.10.11.104", "location": "http://10.10.11.104:3000/", "attributes": { "ZAP_BASE_URL": "http://10.10.11.104:3000/", "ZAP_SPIDER_MAX_DEPTH": 1 } } ]
I am not sure which warning/error in the following log is the cause for zap to stay Scanner after finishing "Run OWASP Zap Spider" in the engine.
I see the following in the zap-container-logs:
The text was updated successfully, but these errors were encountered: