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.
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.
PerimeterX Custom Application ID (appID) in the format of PX__.
JWT token used for REST API.
The key used for cookie signing.
A Boolean flag to enable/disable the PerimeterX Enforcer.
By default, the PerimeterX enforcer’s mode is set to monitor (0). To activate blocking mode, set the
PMUSER_PX_MODULE_MODE property variable to 1.
Sensitive Routes trigger a server call to PerimeterX servers every time the route is called, regardless of viewing history.
URL to a Custom CSS file for the block page.
URL to a Custom JS file for the block page.
Custom logo to display at the top of the block page.
Max-height = 150px, Width = auto.
Updated 7 months ago