Invalid JWT token (nrf cloud location services)

[Mustafa]

Hello there, 

I'm trying to get a GNSS sample working on thingy91 but I always get invalid jwt in the logs output. 

The steps I have done so far: 

1- updated modem firmware to 1.3.5

2- generate private keys using

AT%KEYGEN=16842753,2,0

3- parse the output using modem_credentials_parser.py 

           
4- create a csv file
                         

 [device_uuid, device_public_key]

5- uploaded via the portal https://nrfcloud.com/#/register-keys

so far no sucess with getting AGPS and PGPS services working using gnss sample.

I'm not sure if I missed a step here.

Appreciate any help!

sdk: v2.4.0
dk: thingy91

    

[Charlie]

Hi Mustafa,

Please follow the process mentioned in (+) nRF Cloud Access Provisioning - Software and Protocols - Cellular IoT guides - Nordic DevZone (nordicsemi.com)

You can simply use utils/python/modem-firmware-1.3+ at master · nRFCloud/utils (github.com) to do provision and play with nRF9160: GNSS — nRF Connect SDK 2.4.1 documentation (nordicsemi.com).

Best regards,

Charlie

[Mustafa]

Hello Charlie, 

Thanks for the answer. As I understood from this documentation. there is no need to provision devices if devices just want to use location cloud services. the provisioning process is only needed if the device is gonna use MQTT messages or FOTA. right?

so back to my original question, GNSS sample uses only location cloud services, so I just need to register the device's public key in the nrf-cloud, so no need to add CA, is it correct?

Best regards,

Mustafa

[Charlie]

Hi Mustafa,

Mustafa said:

the provisioning process is only needed if the device is gonna use MQTT messages or FOTA. right?

My understanding of provision here is the process to help nRF9160 devices get access to nRF Cloud services, so you do need to do provision to get nRF9160 devices prepared in order to use any nRFCloud services.

Mustafa said:

so I just need to register the device's public key in the nrf-cloud, so no need to add CA, is it correct?

For the nRFCloud location service, You can obtain location data either through the MQTT API or REST API. I only reply the REST API related method for you in the last reply.

For MQTT API/FOTA service, it uses a two-way TLS connection, so you need the device and server to have the following authentication files. 

• Device (client)
  • nRFCloud CA (AWS RooT CA)
  • Device certificate with Public Key
  • Device Private Key for decryption (MQTT/FOTA)
• nRF Cloud (server)
  • Device CA from providers / Device certificate (MQTT/FOTA)
  • nRF Cloud certificate with Public Key
  • nRF Cloud Private Key for decryption

nRF9160: nRF Cloud MQTT multi-service — nRF Connect SDK 2.4.1 documentation (nordicsemi.com) demonstrates the usage of nRF Cloud service through MQTT API.

Best regards,

Charlie

[Mustafa]

Hi Charlie,

I tried the Python scripts (nrf_cloud_provision.py) and (device_credentials_installer.py). 

I got success response from the provision request

but I still get this error log in GNSS sample

,

I tried it with two dks and the same result even though I upgraded my plan subscription and still doesn't work!

Best regards,

Mustafa

[Charlie]

Hi Mustafa,

Did you use the default value of the nRF9160's UUID as the CN in the credential? If yes, you should have the following configuration in prj.conf.

CONFIG_NRF_CLOUD_CLIENT_ID_SRC_INTERNAL_UUID=y

Best regards,

Charlie

[Mustafa]

Hi Charlie, 

You are right that was what I missed!

Many thanks the problem is solved