zaproxy
zaproxy copied to clipboard
Accessing remote daemon instance using local instance as UI
Is your feature request related to a problem? Please describe.
Operating a remote zaproxy instance running in daemon mode.
Describe the solution you'd like
Being able to connect a locally running zaproxy instance as user interface to a proxy instance in daemon mode for remote control.
Describe alternatives you've considered
The API interface is accessible programmatically, however being able to use the existing graphical interface would be nice.
Screenshots
No response
Additional context
Would be the idea of logically separating backend / frontend via API access.
Would you like to help fix this issue?
- [ ] Yes
You can start ZAP with GUI and still access the ZAP API, there's also Webswing.
The given in this case would be that there is a backend, daemonized 24x7 (zap-)proxy that sits between user and application, running on a headless server. The wish would be the ability to connect another interactive interface instance from where a GUI is available on demand which happens to be implemented in the same code / binary to that other backend instance that is watching the traffic.
I think theres zero chance of us changing the ZAP desktop to connect to a remote instance of ZAP. I like the idea, but it would be way too much work for us to consider. It will of course be possible to implement a web UI on top of the ZAP API - I think thats a better alternative. Again, not something I can see any of the Core Team working on right now (unless they want to of course;). But at least thats something that someone else could implement...