Perforce

Perforce BlazeMeter 4.2: Control API Monitoring access and create correlated JMeter scripts

Perforce BlazeMeter 4.2 adds SSO group controls for public API Monitoring buckets and makes AI Auto Correlation generally available. Teams can upload browser-recorded HAR files, review correlation health, and produce JMeter .jmx scripts while Taurus Cloud addresses seven identified vulnerabilities.

By Chris CarpenterBlazeMeterTest AutomationDevSecOps
perforce-logo.svgPerforce BlazeMeter Logo Transparent.png
Perforce BlazeMeter 4.2: Control API Monitoring access and create correlated JMeter scripts cover graphic
Back to Perforce release updates
Release facts
VendorPerforce
ProductBlazeMeter
Version4.2
Vendor release dateOctober 26, 2026
Published by MeritoOctober 26, 2026
Vendor release notesBlazeMeter 4.2 release notes
Release historyBlazeMeter release history

Account admins can now limit an SSO group's access to selected public API Monitoring buckets, so members see only the buckets assigned to their group.

Restrict SSO groups to API Monitoring buckets

BlazeMeter 4.2 lets account admins select the public API Monitoring buckets available to each SSO group. A user in a group with selected buckets can view only those buckets. The selection is managed through BlazeMeter group management.

Create JMeter scripts from HAR files with AI Auto Correlation

Performance engineers can use generally available AI Auto Correlation with HAR files recorded in a browser. After a HAR upload, BlazeMeter detects and correlates dynamic values in the traffic, creates extractors and injectors, and shows each file's correlation health on the Analysis tab.

When users finalize the work, BlazeMeter creates a JMeter .jmx script. In most cases, it correlates all dynamic values automatically. Users can review the result and manually correlate values that remain before finalizing.

Address identified Taurus Cloud vulnerabilities

Taurus Cloud 2.4.556-reduced applies fixes and removes affected components for seven identified vulnerabilities:

  • CVE-2026-102276 and CVE-2026-102278: high-severity brace-expansion issues in npm
  • CVE-2026-106445 and CVE-2026-106446: critical handlebars issues used by Newman
  • CVE-2026-93748: a high-severity http-cache-semantics issue in npm
  • CVE-2026-97687 and CVE-2026-97689: high-severity urllib3 issues in Python

The 4.2 release summary also references Taurus Cloud version 2.4.543-reduced.

What this means for your team

QA teams can apply SSO group visibility to the public API Monitoring buckets relevant to each group. Performance testers can begin with recorded browser traffic, inspect AI correlation health, resolve any remaining dynamic values, and finalize a JMeter script. This gives managers a defined review point before teams use generated test scripts in automated testing work.

Based on the official Perforce release notes.

How Merito helps

Merito can help teams adopt and govern BlazeMeter workflows through managed services. See also BlazeMeter 4.1.

Merito is an authorized Perforce reseller and services partner. Our Perforce BlazeMeter team helps you adopt the 4.2 changes, with implementation services to configure them for your environment and training and enablement to bring your teams up to speed.

About BlazeMeter

BlazeMeter licenses, renewals, upgrades and implementation are available through Merito, an authorized Perforce reseller and services partner.

Frequently Asked Questions