Incorrect authentication credentials

Add-ons Development
#1

headers: { Authorization: ‘’, Accept: ‘application/json’ } }
JPM [debug] [API] <- { headers:
{ allow: ‘GET, PUT, HEAD, OPTIONS’,
‘content-type’: ‘application/json’,
date: ‘Mon, 25 Jan 2016 10:37:05 GMT’,
server: ‘nginx’,
‘set-cookie’: ‘’,
‘strict-transport-security’: ‘max-age=31536000’,
vary: ‘Accept, X-Mobile, User-Agent’,
‘www-authenticate’: ‘JWT realm=“api”’,
‘x-frame-options’: ‘DENY’,
‘content-length’: ‘51’,
connection: ‘Close’ },
response: { detail: ‘Incorrect authentication credentials.’ } }
JPM [error] FAIL
Error: Received bad response from the server while requesting https://addons.mozilla.org/api/v3/addons/test-1%40wisestamp.com/versions/4.8.20.14/

status: 401
response: {“detail”:“Incorrect authentication credentials.”}
headers: {“allow”:“GET, PUT, HEAD, OPTIONS”,“content-type”:“application/json”,“date”:“Mon, 25 Jan 2016 10:37:05 GMT”,“server”:“nginx”,“set-cookie”:[“multidb_pin_writes=y; expires=Mon, 25-Jan-2016 10:37:20 GMT; Max-Age=15; Path=/”],“strict-transport-security”:“max-age=31536000”,“vary”:“Accept, X-Mobile, User-Agent”,“www-authenticate”:“JWT realm=“api””,“x-frame-options”:“DENY”,“content-length”:“51”,“connection”:“Close”}

at C:\Users\uriwise\AppData\Roaming\npm\node_modules\jpm\lib\amo-client.js:85:13
at tryCatchReject (C:\Users\uriwise\AppData\Roaming\npm\node_modules\jpm\node_modules\when\lib\makePromise.js:845:30)
at runContinuation1 (C:\Users\uriwise\AppData\Roaming\npm\node_modules\jpm\node_modules\when\lib\makePromise.js:804:4)
at Fulfilled.when (C:\Users\uriwise\AppData\Roaming\npm\node_modules\jpm\node_modules\when\lib\makePromise.js:592:4)
at Pending.run (C:\Users\uriwise\AppData\Roaming\npm\node_modules\jpm\node_modules\when\lib\makePromise.js:483:13)
at Scheduler._drain (C:\Users\uriwise\AppData\Roaming\npm\node_modules\jpm\node_modules\when\lib\Scheduler.js:62:19)
at Scheduler.drain (C:\Users\uriwise\AppData\Roaming\npm\node_modules\jpm\node_modules\when\lib\Scheduler.js:27:9)
at nextTickCallbackWith0Args (node.js:433:9)
at process._tickCallback (node.js:362:13)

I checked and our credentials are correct.

#2

I blindly guess this is a timing issue. Try syncing your clock to NTP then trying agian. I had this same issue:

Related issues I think:

#3

After taking my clock one minute back, it worked. However this should work also with the clock adjusted.

#4

Yeah it’s a common request, but it’s the design/nature of JWT.