Persistent Authorization Failed Error (Using nodejs sdk asposewordscloud@25.3.0 )

Aspose.Words Cloud Product Family
1

I am experiencing continuous authorization failures when using the Aspose Words Cloud NodeJS SDK (version 25.3.0) since [2025-04-10 16:55:02] (UTC+0). The system has encountered approximately 10 “Authorization failed” errors. Prior to this occurrence, everything was functioning properly.

I only discovered the issue on 2025-04-10 21:18:29 (UTC+0) and manually restarted the application, after which the requests returned to normal operation. However, I am uncertain whether the restoration was directly due to my restart action or due to other factors.

Below is the error log:

"error":"Error","message":"Authorization failed"},"stack":"Error: Authorization failed\n    at /***/node_modules/.pnpm/asposewordscloud@25.3.0/node_modules/asposewordscloud/dist/internal/requestHelper.js:80:31\n    at Generator.throw (<anonymous>)\n    at rejected (/***/node_modules/.pnpm/asposewordscloud@25.3.0/node_modules/asposewordscloud/dist/internal/requestHelper.js:32:65)\n    at processTicksAndRejections (node:internal/process/task_queues:95:5)"

I am unable to troubleshoot this issue effectively as the access token for Aspose is managed internally by the Aspose NodeJS SDK. I cannot determine what access tokens were being used during these failed authorization attempts or verify their expiration details.

Could you please investigate this issue and advise on potential solutions? Is there a known problem with token management in this SDK version?

Thank you for your assistance.

2

Sorry for the inconvenience, I shared that error with the billing team, so they investigate this issue.

3

We’re having authorization issues too (returning NULL from getAccessToken())

4

We have been having auth issues since today ~21:30UTC {“Message”:“Authentication failed!”}
Troubleshooting it appears that https://api.aspose.cloud/v4.0/words most recent version works while any previous version ie https://api.aspose.cloud/v1.1/words does not

5

I will ask the responsible team about authorization for the 1.1 version, but you should consider moving on to the v4.0 version. v1.1 is old, and we do not support it anymore. It just stays online, we do not update it, and we do not fix any bugs there.
UPD: The legacy version is restarting and will be available in 20 minutes.

1 Like