Pzc token handling at runtime in jmeter test

Hi

We are trying to test pega 24.2 constellation application using jmeter we found there is pzctkn in request header which is dynamically changing every time when login to application so we wanted to correlate pzctkn in order to handle at runtime but there is no such value from server response to correlate. Can you please help us with details about pzctkn like how it generates when login and source code of the pzctkn

@SudheerG17359477To handle the pzctkn in JMeter for Pega 24.2 Constellation applications, inspect the server’s responses after login to locate the token. It might be found in cookies, JavaScript, hidden fields, or response headers. Use tools like JMeter’s Regular Expression Extractor, JSON Extractor, or Boundary Extractor to capture the token dynamically. If it’s a cookie, enable the HTTP Cookie Manager to manage it automatically. Once extracted, save the token to a variable (e.g., ${pzctkn}) and include it in the headers of subsequent requests using the format pzctkn: ${pzctkn}. If the token isn’t visible, check JavaScript in the application to understand how it’s generated or consult Pega documentation for guidance. Use browser developer tools or tools like Fiddler to debug the request-response flow for better insights

@SudheerG17359477

When you decode “Set-Cookie” (which has value starting as “Pega-AAT=”) from the response header , you can see a attribute called “csrf” in the token payload , that is the Pzctkn to be passed in the subsequent request header.