Getting Started
To get started with Real-time protection integration, you should have completed the integration in Monitor mode and received the initial traffic report from the ShieldSquare Service.
| Info |
|---|
Note : Before getting started with the Real-time protection, make sure that you have gone through the configurations to be done in Monitor Mode. |
...
Integration in Real-time protection prevents bots in real-time. In this mode, every API call is responded to with an appropriate response code that indicates the action to be taken on the incoming request.
| Info |
|---|
Note : All the API calls made in this mode will be synchronousbe synchronous. |
Follow these steps for integration in Real-time Protection.
...
The next step is to make a few modifications in the code that makes the API call to ShieldSquare Service. This step assumes that you have already integrated API Call in Monitor mode.
| Info |
|---|
There will be no change in the JS code when switching modes. |
The API call shieldsquare_ValidateRequest(username, calltype) will take the following parameters as inputs:
...
Move Changes to Production
| Code Block | ||
|---|---|---|
| ||
config.sid =“YourProduction ID”
config.mode ="Active"
config.async_http_post =true
config.timeout_value =100
config._ipaddr ="auto"
config.ss2_domain ='ss_sa.shieldsquare.net'
config.domain_ttl =3600
config.domain_cache_file ='/tmp/'
config.deployment_number ='1234'
config.ip_index = 1
config._support_email = "botmanager_support@radware.com"
config._redirect_domain = "validate.perfdrive.com"
config._ss_block_enabled = true
config._ss_captcha_enabled = true
config._sessid = "" |
In order to move changes to production, replace_sidparameter ( in the ss2_config file) with the Production ID. It takes about 2-3 hours for the production data to reflect in the ShieldSquare Dashboard.
...