NOTEYou can use the
ssd api-management add api-interceptor sql-threat-protectioncommand or its shortened versionssd apim add api-interceptor sql-threat-protection.
The ssd api-management add api-interceptor sql-threat-protection command can be followed by flags with their corresponding arguments:
If no flag is specified, the interactive mode will be activated.
Below you will find usage examples in the direct mode:
The following flags can be used with the ssd api-management add api-interceptor sql-threat-protection command:
Flag | Type | Description |
|---|---|---|
| Flags for APIs | ||
| -n, --api-name | string | API name to which the interceptor will be added |
| -s, --revision | string | API revision to which the interceptor will be added |
| -v, --api-version | string | API version to which the interceptor will be added |
| Other flags | ||
| -b, --blocks | The Request/Response block that will be protected. E.g.: "body", "headers", "query params", "cookies" or "path params" | |
| -e, --ignore-expression | The expressions that will be ignored. This parameter can be entered several times, so that the multiple expressions are supported. Open text values. E.g.: -e expression1, -e expression2, etc. | |
| --ignore-multipart-form-data | Ignores the body when the Content-Type is multipart/form-data. This flag does not require values (when informed, the default is True) | |
| -f, --flow | string | API flow to which the interceptor will be added (INBOUND or OUTBOUND) |
| -h, --help | Displays help for the command | |
| -m, --method | string | Method (operation) to which the interceptor will be added (Optional). E.g.: POST |
| -a, --path | string | Operation path to which the interceptor will be added (Optional). E.g.: /users |
| -p, --position | int | Position of the interceptor in the API flow |
| -r, --resource | string | Resource name to which the interceptor will be added (Optional) |
Flag | Type | Description |
|---|---|---|
| -c, --config | string | Configuration file (default: $HOME/.sensedia/config.json) |
| --profile | string | The configuration profile you want to use (default: "default") |
| --verbose | Lists all requests made by the command. It is possible to store this information in a TXT file instead of displaying it on the terminal. E.g.: $ ssd (api-management | apim) list apis --verbose 2> log.txt |
We use cookies to enhance your experience on our site. By continuing to browse, you agree to our use of cookies.Learn more