First Party Configuration

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

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

To confirm that you have configured your 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 Enforcer:

1http_filters:
2 ...
3 - name: perimeterx
4 typed_config:
5 "@type": type.googleapis.com/udpa.type.v1.TypedStruct
6 type_url: type.googleapis.com/perimeterx.Enforcer
7 value:
8 px_enabled: true
9 px_appid: "<APP_ID>"
10 px_cookie_secret: "<COOKIE_SECRET>"
11 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 Enforcer

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

1http_filters:
2 ...
3 - name: perimeterx
4 typed_config:
5 "@type": type.googleapis.com/udpa.type.v1.TypedStruct
6 type_url: type.googleapis.com/perimeterx.Enforcer
7 value:
8 px_enabled: true
9 px_appid: "<APP_ID>"
10 px_cookie_secret: "<COOKIE_SECRET>"
11 px_auth_token: "<AUTH_TOKEN>"
12 px_first_party_disabled: true
13...

In order to enable First-Party Mode, you need to set the px_first_party_disabled to false (or remove that configuration parameter at all) 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.