Ability to provide values for OpenAPI schema types

Is your feature request related to a problem? Please describe.

The OpenAPI import add-on uses a predefined hashmap for default values to use if no values are specified as example.
That presents an issue for endpoints like /accounts/{account_id}/remove where an example value might change between each testing, and the default 10 for integers is most likely wrong.

Describe the solution you’d like

An options menu like the existing Form Handler, that will also let users programmatically set OpenAPI values for each type before running ZAP.

Describe alternatives you’ve considered

Setting example values for each endpoint’s types for ZAP to use, but editing the openapi spec file before each run is a slowdown if ZAP is used as a DAST in an SDLC.

Screenshots

No response

Additional context

No response

Would you like to help fix this issue?

• Yes

[vx-sec]

Works like a charm, should have RTFM. 😃 For example in case of /accounts/{account_id}/remove, you just specify account_id as a field name and give it a value in form handler. Closing.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.