Changelog

Version 5.5.1

Added

• Added orig_cookie_vid field on all enforcer activities

Version 5.5.0

Added

• Added is_sensitive_route field to risk api and async activities
• Added custom_sensitive_request feature support
• Added request_id field in telemetry activity

Fixed

• Fixed a bug where cookie operation order mismatched the spec, causing expired high-score cookies to trigger block instead of risk

Version 5.4.1

Internal

• Added additional updateReason RISK to Telemetry flow

Version 5.4.0

Internal

• Added Documentation enforcement workflow - verify that the documentation is up to date with the latest changes in the codebase
• Telemetry By Risk Support
• Added Telemetry By Risk support

Version 5.3.0 -

Internal

• Added remote config CI workflow support

Version 5.2.1

• Aligned remote config ID field (px_remote_config_id -> remote_config_id) and added it to all activities
• Added remote config version field on all activities

Version 5.2.0

• Updated GraphQL logic to match spec and added functionality:
  • Added keywords extraction, including custom extraction
  • Updated logic of operationName query operations filtering
  • Updated parsing logic of multiple operations in the same query
  • Removed empty fields from activities
• Changed order of cookie verification steps to accommodate research severity definitions
• Added hard block page response template
• Added AdditionalActivityHandler example
• Removed S2SCallReason none
• Modified check of empty risk response to not use UUID
• Modified first party captcha script fetching to always get script with params
• Changed default value of bypass monitor header to x-px-block
• Added CI support including end to end tests and fuzzing
• Added CI multi-config for default, advanced and monitor modes

Version 5.1.0

• Support multiple config types (active, static, remote)
• Modify telemetry activity to include all types of config
• Fixed module mode default value and refactored according to spec (monitor and active_blocking instead of true false)

Version 5.0.2

• Added exponential backoff mechanism for retrying remote config updates when errors occur

Version 5.0.1

• Added errorType field to error logs during failed remote config updates