ZAP as a windows service?

[Justin Holbrook]

Hi. I'm trying to stand up ZAP on a standalone machine so that I can leverage as part of a release process for multiple applications. Right now I have it running in -daemon mode which is ok for testing. I'd feel better if it was running as a windows service or if I had some visibility as to the health of ZAP. The only way I have been able to identify the zap process is by comparing process lists and noticing there was a javaw process when zap is running in the background. I tried installing zap as a service using NSSM, but the service won't start.

Am I missing the point here or just trying to do something ZAP is not set up for? I need visibility to the state of the process so that if it goes down I can address recovery. I can't wrap automation around this otherwise whenever something happens to the process it will be difficult to troubleshoot.

Has anyone had luck running ZAP in this fashion? I'm not opposed to running it on a different OS if that helps.

[Simon Bennetts]

We have an open issue for supporting ZAP as a Windows service: https://github.com/zaproxy/zaproxy/issues/392
I'm not aware of anyone working on this, so volunteers welcome :)

ZAP was originally a desktop tool.
We are changing it so that it can be run as a long running service, but we havnt addressed things like this yet.

Cheers,

Simon