Hi Manisha,

If you get a CSRF error, it likely means that the macros used by the users are just replaying the HTTP POST calls to PPM that were initially recorded, instead of interacting with the PPM UI. As a result, the recorded POST messages will include CSRF Tokens parameters that was only valid at the time of the recording, and trying to re-submit them later in a different session will cause this error.

I don't really have a solution for that - you're not supposed to re-submit old CSRF token - this is a protection mechanism that protects PPM users again CSRF attack, so you don't want to disable this.

I see two possible solutions:

1) Change the macro (or eventually use a different macro tool) that would click UI elements in a browser instead of just replaying POST HTTP requests.

2) Update the macro script to read the new CSRF token value in their active session (you can read the value from the ppm CSRF cookie for example, or can find it in the source of the web page that's about to submit the POST request), and use that value in the CSRF parameter of the replayed POST message instead of the recorded outdated one. But whether that's possible and how to do that depends on the macro tool used, and unfortunately that's not something I can help with.