Problem With nRF9151DK running the Location sample app

[nipri]

I am on the learning curve of nRF9151 and LTE/GNSS.

Trying to build and run the sample app under nrf/samples/nrf9160/location

The errors Im getting are

[00:11:23.476,623] <err> nrf_cloud_codec_internal: REST error msg: Auth token is malformed.
[00:11:23.485,626] <err> nrf_cloud_rest: nRF Cloud REST error code: 40100
[00:11:23.492,980] <err> nrf_cloud_rest: REST request was rejected. Response status: 401
[00:11:23.501,708] <err> nrf_cloud_rest: Response body: {"message":"Auth token is malformed.","code":40100}
[00:11:23.512,390] <err> location: Failed to acquire location using cloud location, error: -77
[00:11:23.521,606] <err> location: Location acquisition failed and fallbacks are also done
Getting location failed

My DK is successfully provisioned in nRFcloud.

I want to learn more about how to properly configure and credential my DK from...

docs.nordicsemi.com/.../README.html

... however, the following links in this page are broken

This sample uses the nRF Cloud REST API, which requires that your device has a valid signing key installed and registered with nRF Cloud.

(See nRF Cloud REST API and Securely generating credentials on the nRF9160 for more details on this requirement). 

[Nishant Gaurav]

It seems you are facing a token authentication issue. How did you provision your DK to nRF Cloud? If you used an AT Token or a specific provisioning script, the device might be trying to authenticate using its IMEI while the Cloud expects its UUID.

Try adding these specific lines to your prj.conf file. This forces the device to use its internal UUID as the Client ID, which often resolves the 'Malformed Token' error:

# Use the internal UUID instead of IMEI for identification
CONFIG_NRF_CLOUD_CLIENT_ID_SRC_INTERNAL_UUID=y
CONFIG_NRF_CLOUD_CLIENT_ID_PREFIX=""