Question
IN
Last activity: 25 Aug 2025 16:24 EDT
Pega Application Pega-Perf=itkn=1 cookie issue
In the Pega EDN Application, the cookie Pega-Perf=itkn=1 is set in the request header of a GET call within the login flow, and its value changes randomly.
This cookie is not present in any response header; it appears only in the request header, which prevents us from correlating the APIs in JMeter for Performance Testing. Since this API is part of the login process, we are unable to proceed further without resolving this dependency.
We kindly request your support in resolving this issue.
HCA Healthcare
US
This cookie is a client-side perf flag set by Pega’s UI JavaScript during login; it isn’t required for authentication and the server doesn’t echo it back, so JMeter can ignore it. First, verify it’s nonessential: in a browser, delete the Pega-Perf cookie and reload login; if everything still works, you’re safe to drop it in tests. In JMeter, add an HTTP Cookie Manager and do not define Pega-Perf; this prevents a random value from appearing and keeps flows correlatable. If your scripts still see a Cookie header, add an HTTP Header Manager to explicitly set Cookie without Pega-Perf for those requests. If your app insists on the cookie, hard-code a stable one in Cookie Manager (name=Pega-Perf, value=itkn=1, domain=your host, path=/) so it stops changing. For non-prod, you can also ask the platform team to disable the browser performance cookie/collector via a DSS or system setting so it never gets set during load tests. Document whichever path you choose so future runs stay consistent.
IN
@Sairohith Thanks for the Update.
We have tried all the possible approaches you mentioned, but we are still not getting the expected response as in the application:
- Manually deleted the Pega-Perf cookie in a browser and reloaded the login page — the login still worked successfully.
- Added an HTTP Cookie Manager without defining Pega-Perf.
- Added an HTTP Header Manager and explicitly set the Cookie header without Pega-Perf for those requests.
- Hard-coded a stable Pega-Perf value in the Cookie Manager.