Module Configuration

Required Apache Configuration

The following Apache Configurations are required to support the PerimeterX Apache module:

  • px_enabled
  • px_appId
  • px_cookie_secret
  • px_auth_token
# == Required Parameters ==
px_enabled On
px_appId <PX_APP_ID>
px_auth_token <PX_AUTH_TOKEN>
px_cookie_secret <COOKIE_ENCRYPTION_KEY>
  • px_appId - The PerimeterX custom application id in the format of PX__ .
  • px_cookie_secret - The key used by the cookie signing page. The Cookie Key is generated in the PerimeterX Portal Policy page.
  • px_auth_token - The JWT token for REST API. The Authentication Token is generated in PerimeterX Portal the Platform Settings -> Application page.

Apache Configuration Example

The following default.conf example contains the minimum required configuration for the PerimeterX Apache module:

<VirtualHost *:80>

  px_enabled On
  px_appId APP_ID
  px_cookie_secret COOKIE_SECRET
  px_auth_token AUTH_TOKEN

  ServerAdmin [email protected]
  DocumentRoot /var/www/html

  # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
  # error, crit, alert, emerg.
  # It is also possible to configure the loglevel for particular
  # modules, e.g.
  #LogLevel info ssl:warn

  ErrorLog ${APACHE_LOG_DIR}/error.log
  CustomLog ${APACHE_LOG_DIR}/access.log combined

  # For most configuration files from conf-available/ that are
  # enabled or disabled at a global level it is possible to
  # include a line for only one particular virtual host. For example, the
  # following line enables the CGI configuration for this host only
  # after it has been globally disabled with "a2disconf".
  #Include conf-available/serve-cgi-bin.conf