You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in the RapiDAST configuration file, it seems that scanners.zap.apiScan.apis.apiUrl only support single value:
config:
configVersion: 4# `application` contains data related to the application, not to the scans.application:
shortName: "APP_SHORT_NAME"url: "https://kubernetes.default.svc"# to be replaced with your cluster API server URL
...
scanners:
zap:
# define a scan through the ZAP scannerapiScan:
apis:
apiUrl: "https://MY_ENDPONIT/openapi/v3/apis/MY_CRD/v2"# to be replaced with your API group information
...
I'm wondering if we could set multiple apiUrls in one config file. In some scenarios, users may want to scan multiple API groups. If there are no differences except for the scanners.zap.apiScan.apis.apiUrl field, they may need to create and apply multiple files repeatedly.
Possible solutions
Not quite familiar with the codebase, one possible way may be to convert the schema to an array:
Background
Currently in the RapiDAST configuration file, it seems that
scanners.zap.apiScan.apis.apiUrl
only support single value:I'm wondering if we could set multiple apiUrls in one config file. In some scenarios, users may want to scan multiple API groups. If there are no differences except for the
scanners.zap.apiScan.apis.apiUrl
field, they may need to create and apply multiple files repeatedly.Possible solutions
Not quite familiar with the codebase, one possible way may be to convert the schema to an array:
It would be nice to have this kind of feature. Alternatively, is there any suggested workaround?
The text was updated successfully, but these errors were encountered: