nRF Cloud Authentication Issue

Hi,

I have several deployed devices that have been running for a while, using the nRF Cloud A-GNSS system with the nRF Location library. These devices were successfully provisioned with nRF Cloud, and their public keys were uploaded. They had been functioning properly for about a month, but starting a few days ago, I suddenly began receiving authentication errors.

There have been no changes to the firmware or nRF Cloud configurations. My NCS version is 2.6.0, and the modem firmware version is 1.3.6. I used the AT%KEYGEN command to generate credentials and uploaded the decoded credentials to nRF Cloud, following the official tutorial.

Is there an issue with nRF Cloud that could be causing this problem?

[00:00:17.189,361] <dbg> rest_client: rest_client_http_response_cb: HTTP: All data received (content/total: 51/287), status: 401 Unauthorized
[00:00:17.189,392] <dbg> rest_client: rest_client_request: API call response len: http status: 401, 51 bytes
[00:00:17.189,392] <dbg> rest_client: rest_client_close_connection: Socket with id: 0 was kept alive and wasn't closed
[00:00:17.189,605] <err> nrf_cloud_codec_internal: REST error msg: Auth token is malformed.
[00:00:17.189,666] <err> nrf_cloud_rest: nRF Cloud REST error code: 40100
[00:00:17.190,704] <err> location: nRF Cloud A-GNSS request failed, error: -77

[Update]: Our logs show that the last successful request to nRF Cloud was on February 5, 2025, at 02:20:30 UTC. Since then, all requests have been rejected due to authentication errors. There is a maintenance report for nRF Cloud on the same day: https://status.nrfcloud.com/maintenance/507661. I wonder if this could be the cause of the issue.

  • Hi Kevin_nik,

    If this issue is still on, could you please tell what is your tenant_id and what are these devices? Either their deviceId or Device UUID. Also in the log it says that Auth token is malformed, what is the token type you are using.

    These will help us solve the issue.

    Thanks,

    Markku Lehto