Answered question

How to handle nonce value in neoload?

I have a request that holds a NONCE value. I couldn't correlated the value since its not found to be in any of the previous responses.
Is there a way Neoload could generate a perfect Cryptographic nonce value? or anyother method to handle NONCE?

I don't want to confuse Timestamp & Cryptographic nonce , Hence I Tried with timestamp method like Epoch time, custom time and even UDDI and string generators yet nothing worked.?

Kindly provide a solution?

Looking in the Internet it seems that this once value is only a random string that is then used to sign a call with a key, epoch time etc...

So i think that it is fine to generate that manually through a JS. I found a function here that you could use to generate a 16 digits random string.


Did you find this useful ?

No (0)

Yes (0)

0% of users found this answer useful

Other answers

Hi Nouredine, Thanks For responding.

Its not a SOAP Request.
It is a nonce value at OAuth Get Request.
Kindly find the screenshot detailing the requirement.

Have you confirmed with another recording that this value is different all the time? And does it still not appear in any of the server responses?

In your screen shot i can only see one JS "main-agents.js". So if the value is computed on client side it has to be from that JS or something is missing in your recorded script.


Hi Nouredine,
The value changes at each recording. and at each recording this value is not to be found in any of the responses.
May be the value is computed on client side. If so how to handle it?