First Party Configuration

In First Party Mode, the PerimeterX Apache Enforcer acts as a reverse proxy for client requests and sensor activity. mod_perimeterx is configured with First-Party mode enabled by default. To confirm that you have configured your PerimeterX Apache Enforcer in First-Party mode, review the mod_perimeterx in your Apache configuration.

First Party Enabled Example (default value)

Below is an example of a basic configuration for the mod_perimeterx module.

<IfModule mod_perimeterx.c>
    # basic directives
    PXEnabled On
    CookieKey [COOKIE KEY PLACEHOLDER]
    AppID [APPID PLACEHOLDER]
    AuthToken [AUTHTOKEN PLACEHOLDER]
    BlockingScore 100
    ReportPageRequest On
    IPHeader X-True-IP
    MonitorMode On
</IfModule>
  • If FirstPartyEnabled or FirstPartyXhrEnabled are not found in mod_perimeterx, the First-Party Mode is enabled in the Enforcer. (Continue to the Next Steps below.
  • Otherwise, proceed to the First Party Mode Disabled Example.

First Party Mode Disabled Example

Below is an example of a basic configuration for the mod_perimeterx module.

The presence of the FirstPartyEnabled and the FirstPartyXhrEnabled with values of Off confirm that the default configuration has been changed and First-Party mode is disabled.

<IfModule mod_perimeterx.c>
    # basic directives
    PXEnabled On
    CookieKey [COOKIE KEY PLACEHOLDER]
    AppID [APPID PLACEHOLDER]
    AuthToken [AUTHTOKEN PLACEHOLDER]
    BlockingScore 100
    ReportPageRequest On
    IPHeader X-True-IP
    MonitorMode On
    FirstPartyEnabled Off
    FirstPartyXhrEnabled Off
</IfModule>

In order to enable First Party Mode, you need to set both the FirstPartyEnabled and the FirstPartyXhrEnabled to On and reload your Apache configuration.

After configuring the enforcer to handle First Party requests, complete the steps listed on the Integrate 1st-Party JS Snippet to confirm your snippet is setup to serve the Javascript Sensor via First-Party.


Did this page help you?