Torizon API returns 403 since today

Technical Support
, , ,
1

Hi,

our test application uses the torizon API

But, It stopped working today!
First I thought the bearer token is outdated, so I created a new one as described here:
1.) new client → Torizon Cloud API (Beta) | Toradex Developer Center
2.) new token → Torizon Cloud API (Beta) | Toradex Developer Center

But still, for the requests related to the device metrics the response is 403

image
image1091×833 41.7 KB

The other endpoints seem to work normal

Offline Cache of Fluent-Bit Metrics
2

Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

A 403 Forbidden error typically indicates that the server understood the request but refuses to authorize it. Here are a few steps you can take to troubleshoot and resolve this issue:

  1. Verify Token Validity: Ensure that the token you generated is still valid and has not expired. Tokens have a limited lifetime, and you may need to generate a new one if the current one has expired.

  2. Check Permissions: Make sure that the API client you created has the necessary permissions to access the device metrics. Sometimes, specific permissions are required to access certain endpoints.

  3. Endpoint and Method: Double-check that you are using the correct endpoint and HTTP method (GET, POST, etc.) for the device metrics. Refer to the Torizon Cloud API documentation to confirm the correct usage.

  4. Client Secret: Ensure that the client secret used to generate the token is correct and matches the one provided when the API client was created.

  5. Sandbox vs. Production: If you are using a sandbox environment, ensure that the API client and token are created and used within the same environment. Mixing sandbox and production credentials can lead to authorization issues.

  6. API Changes: Verify if there have been any recent changes or updates to the Torizon Cloud API that might affect the endpoints or authentication mechanisms. Check the Torizon Cloud API documentation or any release notes for updates.

If you have verified all the above and the issue persists, it might be helpful to reach out to Toradex support for further assistance, as there could be an underlying issue with the API service itself.

3

Hi @dan

Thanks for reporting this issue and sorry for any inconvenience.

We just updated our back-end authentication method and it seems that some client_ids permissions didn’t fully migrated to the new format.

Those steps you mentioned should be working in a few hours.

4

Ok after recreation of the client it is working now thanx

1 Like