implement API KEY

[vpereira]

starting on version 2.4.1 api comes automatically configured.

We should support it in all write/destructive actions. For now I'm disabling it and supporting it in the zap initialization. However It's not implemented in any method.. please check https://github.com/vpereira/owasp_zap/blob/master/lib/owasp_zap.rb#L88

[0xff6a]

Have you started working on this yet? If not I would be keen to implement this. I'll raise a PR when done

Cheers,
J

[vpereira]

Hey @foxjerem

no I didn't. Feel free to send me a pull request. The API key is optional, so just make sure that the API works with/without api key.

thanks!

[ninp0]

Is this still an active project?

[vpereira]

Am 06.08.2016 00:26 schrieb "ninp0" [email protected]:

Is this still an active project?

Yes sure. But I cannot force people to contribute :)

@ninp0 to disable the API key isn't an option?

[vpereira]

Hi @ninp0 ,

I don't see a reason why it should be a risk, running in an isolated environment and where an attacker shouldn't reach ZAP directly.

Feel free to send me a pull request. If you decide to do, I think you should add an option to all methods to give the API KEY as parameter and it get used if the object has the api key enabled. To save the API KEY in the object, won't help you, otherwise an attacker could abuse ZAP using the ruby objects anyway..