XSS Threat Protection Interceptor Addition (ssd api-management add api-interceptor xss-threat-protection)

The ssd api-management add api-interceptor xss-threat-protection command allows you to add an "XSS Threat Protection" interceptor to an API flow on Sensedia API Platform.

You can use the ssd api-management add api-interceptor xss-threat-protection command or its shortened version ssd apim add api-interceptor xss-threat-protection.

Usage

The ssd api-management add api-interceptor xss-threat-protection command can be followed by flags with their corresponding arguments:

ssd api-management add api-interceptor xss-threat-protection [flags]

If no flag is specified, the interactive mode will be activated.

Below you will find usage examples in the direct mode:

# Adds an XSS Threat Protection interceptor to the inbound flow of an API for all resources and methods
$ ssd (api-management | apim) add api-interceptor xss-threat-protection --api-name “Open Banking” --api-version “1.0.0” --revision 1 --flow INBOUND --locations-default-regex “uri path,query param,header,body”

# Adds an XSS Threat Protection interceptor to the inbound flow of an API with multiple regex in specific locations
$ ssd (api-management | apim) add api-interceptor xss-threat-protection --api-name “Open Banking” --api-version “1.0.0” --revision 1 --flow INBOUND --regex-uri-path “expression1” --regex-uri-path “expression2” --regex-query-param “expression1” --regex-query-param “expression2”

Available Flags

The following flags can be used with the ssd api-management add api-interceptor xss-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

-d , --locations-default-regex

Applies the Sensedia API Platform standard set of regular expressions at the given locations

-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)

--regex-uri-path

--regex-query-param

--regex-header

--regex-body

These flags have the same purpose: to apply user-entered regular expressions at the given locations, as per flag’s title.

This parameter can be entered multiple times, so that the various expressions are supported.

For example:

--regex-uri-path expression1

--regex-uri-path expression2

Global Flags

Flag Type Description

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`

-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

Thanks for your feedback!

EDIT

Share your suggestions with us!
Click here and then [+ Submit idea]