Configuration

The initial PerimeterX configuration is determined during the installation process.
Once the Enforcer is installed, you can change its configuration through the Akamai Property Editor.

Required Configuration

The PerimeterX Application ID / AppId and PerimeterX Token / Auth Token can be found in the Bot Defender Portal, under Applications.

The PerimeterX Cookie Encryption Key can be found in the Bot Defender Portal, under Policies.

The Policy from where the Cookie Encryption Key is taken must correspond with the Application from where the Application ID / AppId and PerimeterX Token / Auth Token.

PX_APPID


PerimeterX Custom Application ID (appID) in the format of PX__.

PX_AUTH_TOKEN


JWT token used for REST API.

PX_COOKIE_V2_KEY


The key used for cookie signing.

Optional Configuration

PX_ENFORCER_ENABLED

A Boolean flag to enable/disable the PerimeterX Enforcer.

Default: true

PX_MONITOR_MODE_ENABLED

By default, the PerimeterX enforcer is set to "Monitor Only" mode. To activate blocking mode, set the PX_MONITOR_MODE_ENABLED property variable to false.

Default: true

PX_SENSITIVE_ROUTES

Sensitive Routes trigger a server call to PerimeterX servers every time the route is called, regardless of viewing history.

Example: ^(./login/?.)|(./sign/?.)$

Default: Empty

PX_CSS_REF

URL to a Custom CSS file for the block page.

Default: Empty

PX_JS_REF

URL to a Custom JS file for the block page.

Default: Empty

PX_CUSTOM_LOGO

Custom logo to display at the top of the block page.
Max-height = 150px, Width = auto.

Default: Empty


Did this page help you?