First Party Configuration

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

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

To confirm that you have configured your PerimeterX Enforcer in First-Party mode, review the perimeterx http_filters in your config.yaml.

First-Party Enabled Example (default value)

Below is an example of a http_filters entry from a config.yaml file that contains the minimum settings for the PerimeterX Enforcer:

http_filters:
    ...
    - name: perimeterx
        config:
            px_enabled: true
            px_appid: "<APP_ID>"
            px_cookie_secret: "<COOKIE_SECRET>"
            px_auth_token: "<AUTH_TOKEN>"

First-Party Mode Disabled Example

Below is an example of a http_filters entry from a config.yaml file that contains the minimum settings for the PerimeterX Enforcer

The presence of the px_first_party_enabled with a value of false confirms that the default configuration has been changed and First-Party mode is disabled.

http_filters:
    ...
    - name: perimeterx
        config:
            px_enabled: true
            px_appid: "<APP_ID>"
            px_cookie_secret: "<COOKIE_SECRET>"
            px_auth_token: "<AUTH_TOKEN>"
            px_first_party_enabled: false

In order to enable First-Party Mode, you need to set the px_first_party_enabled to true and redeploy 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 confirm your snippet is setup to serve the Javascript Sensor via First-Party.


Did this page help you?