| Discussion Forum: Thread 339280 |
|
 |
| | | Author: | brickotronic  | | Posted: | May 5, 2023 18:59 | | Subject: | TIMESTAMP_REUSED OAuth errors in API | | Viewed: | 54 times | | Topic: | Technical Issues | |
|
| Hi,
did anyone got TIMESTAMP_REUSED authentication errors?
Example: {"meta":{"description":"TIMESTAMP_REUSED: consumerKey:
XXXXXXXXXX timestamp: 1682887142 nonce: 1683475737654","message":"BAD_OAUTH_REQUEST","code":401}}
I'm getting these very regularly especially when doing price guide requests
or adding items to inventory.
It also seems to happen more often at certain times. It seems like, it happens
for more costly operations and probably at peak times.
I'm using the jave code provided on the API Guide (https://www.bricklink.com/v3/api.page?page=auth),
the BLAuthSigner class.
I have to admit that I'm no OAuth expert and I'm just starting looking
into it in more detail. But even getting a "TIMESTAMP_REUSED" error seems
odd to me. Using the same timestamp should be allowed as long as I'm using
a different nonce. Otherwise, I'd only be able to do one request per second.
What's even more hinting to a Bricklink error is that my inventory gets updated
even though, I get this authentication error back. If authentication really fails,
my inventory shouldn't update.
Any help is appreciated.
Cheers, Hannes
|
|
|
|
|
|
|
Austria, Vorarlberg
