Nonce assertion warning in variman log text file

[clove...@gmail.com]

I am using Variman 3.2.4 and the variman_webapp.txt shows this on every request:

10 Nov 2013 09:26:13,771 WARN  [206.131.184.1 ] org.realtors.rets.server.webapp.auth.NonceTable
-> nonce count failed assertion: 1 > 1

Not sure if this harms anything but I don't recall getting this before 3.2.4 (not 100% sure though).  Does anyone have any suggestions as to what this means?  Searching the Variman doc didn't reveal any clues about nonce settings.  Thanks!

[Mark Klein]

On Nov 10, 2013, at 6:45 AM, clove...@gmail.com wrote:

> I am using Variman 3.2.4 and the variman_webapp.txt shows this on
> every request:
>
> 10 Nov 2013 09:26:13,771 WARN [206.131.184.1 ]
> org.realtors.rets.server.webapp.auth.NonceTable
> -> nonce count failed assertion: 1 > 1

What client is causing that?

That's from the digest authentication code that makes sure there isn't
a replay attack happening. (The nonce must be incremented on each
transaction).

[Mark Klein]

On Nov 10, 2013, at 6:45 AM, clove...@gmail.com wrote:

> I am using Variman 3.2.4 and the variman_webapp.txt shows this on
> every request:
>
> 10 Nov 2013 09:26:13,771 WARN [206.131.184.1 ]
> org.realtors.rets.server.webapp.auth.NonceTable
> -> nonce count failed assertion: 1 > 1

So I checked my logs here and see that Rets Connector is doing that
for the initial transaction. But, after the first warning, things seem
to carry along properly. I'm guessing it is Rets Connector that isn't
incremented the nonce during the login handshake.

Probably just noise you can ignore.

[clove...@gmail.com]

Hi Mark, thanks for the info, I'll take a look into what rets client my users are using and see if I can find a solution and if I do, I'll post it here.