First Party Configuration

In First Party Mode, the PxModule acts as a reverse proxy for client requests and
sensor activity.

The PxModule is configured with First-Party mode enabled by default.

To confirm that you have configured your HUMAN ASP.NET Enforcer in First-Party mode, review the PxModule configuration.

First Party Enabled Example (default value)

Below is an example of a basic configuration for the HUMAN PxModule.

<perimeterX>
    <pxModuleConfigurationSection
      enabled="true"
      appId="<PX Application ID>"
      apiToken="<API token>"
      cookieKey="<cookie key>"
      monitorMode="true"
      blockingScore="100"
      >
    </pxModuleConfigurationSection>
  </perimeterX>

• If firstPartyEnabled or firstPartyXhrEnabled are not found in your PxModule configuration block, 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 PxModule module.

The presence of the firstPartyEnabled and firstPartyXhrEnabled with values of false confirm that the default configuration has been changed and First-Party mode is disabled.

<perimeterX>
    <pxModuleConfigurationSection
      enabled="true"
      appId="<PX Application ID>"
      apiToken="<API token>"
      cookieKey="<cookie key>"
      monitorMode="true"
      blockingScore="100"
      firstPartyEnabled="false"
      firstPartyXhrEnabled="false"
      >
    </pxModuleConfigurationSection>
  </perimeterX>

In order to enable First Party Mode, you need to set both the firstPartyEnabled and firstPartyXhrEnabled to true and reload your configuration and continue to the Next Steps below.

Next Steps

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