setStatus() returns "Authentication Required. statusDetailCode 1014"

Hi,

We would like to use setStatus() using "a" and not "aimsid" so we can skip startSession(). The problem with startSession() is that it returns rate limit errors after several calls, and it also makes the user appear online for a moment.

Unfortunately, setStatus() using "a" returns "Authentication Required. statusDetailCode 1014" which, according to the manual, means "Signature is bad, see the signature notes of startSession".

We assume that this is not the case, because we use the same method for signing the startSession() request, which returns successfully.

To summarize, case A works perfectly:
1. clientLogin() works properly (unsigned request).
2. startSession() works properly (signed request).
3. setStatus() using "aimsid" works properly (signed request).

However, case B results in an error:
1. clientLogin() works properly (unsigned request).
2. (no startSession() call)
3. setStatus() using "a" returns "Authentication Required. statusDetailCode 1014" (signed request).

We do not understand why this is happening, since the same method is used for signing the setStatus() request in both cases (and the startSession() request in case A).

It would be very helpful if you can assist with this.

Thank you,

Best Regards,
Norbert Mocsnik

Hi Norbert - I'm going to work through a couple of test cases to reproduce
and possibly escalate to the appropriate team when I can illustrate the
issue. I'll post an update here for you soon.