Skip to content
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

Unable to access ZAP API over HTTPS #18

Open
604kev opened this issue May 8, 2018 · 5 comments
Open

Unable to access ZAP API over HTTPS #18

604kev opened this issue May 8, 2018 · 5 comments
Assignees
Milestone

Comments

@604kev
Copy link

604kev commented May 8, 2018

The plugin doesn't seem to accept an HTTPS URL for the ZAP API. The "ZAP API URL" field note reads: "The fully qualified domain name (FQDN) with out the protocol. (Eg. zap.example.com)" and attempting to add "https://" as a prefix causes the scan to fail entirely with a network timeout. If the API exposes HTTP as well as HTTPS then it is accessed over tcp/80 only (confirmed in Wireshark).

Is there any way to require HTTPS for the ZAP API URL?

Thanks.

@kasunkv
Copy link
Owner

kasunkv commented May 15, 2018

@604kev At the moment, you are not able to use a HTTPS URL for the ZAP API. This improvement will be made in an up coming update. I'll keep you updated here.

@kasunkv kasunkv self-assigned this May 15, 2018
@kasunkv kasunkv added this to the v3.0 milestone May 15, 2018
@604kev
Copy link
Author

604kev commented May 15, 2018

@kasunkv Thank you for the response, and I'm looking forward to seeing this added.

@mrpolaris
Copy link

Any Updates on when this will be an option

@MrBeanzy
Copy link

+1 for this

@MrBeanzy
Copy link

@kasunkv - Any idea when this will be possible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants