Error CSR when fleet_telemetry_config create about fleet-telemetry HOT 4 CLOSED

Thanks a lot @patrickdemers6, it's done for this part.

Just one very strange thing. I got this when I wanted to add the public key to the vehicle. However, I do have access to this vehicle, and I can make API calls on it etc. And I've already done the ‘third_party’ and ‘authorization_code’ parts. (also with vehicle_device_data scope)

Maybe it's another zone problem? (for the translation of the pictures it's : The vehicle cannot be shared.
Adding a virtual key for ‘bib-data.fr’ is prohibited because you have not granted ‘bib-data.fr’ access to your account.)

from fleet-telemetry.

To add some information:
For the request: "{{FLEET_API_URL}}/api/1/vehicles/{{vehicle_tag}}/fleet_telemetry_config" the answer is "true" (see the screen)

We are unable to check for the errors:
While doing the request
"{{FLEET_API_URL}}/api/1/partner_accounts/fleet_telemetry_errors", here is the answer we get
{ "response": null, "error": "Expected partner account token type", "error_description": "", "txid": "a1e27bf8341e8871d86337837009eb7e" }

Thank you for your help

from fleet-telemetry.

@themarch you first setup your account in NA region, but then set up in EU. I've applied the signed certificate to your account in EU so you should now be able to setup fleet-telemetry.

from fleet-telemetry.

@Martucci98 you are passing a third-party token to the fleet_telemetry_errors endpoint. It requires a partner token. Please see the Authentication section of the docs to learn the differences between these tokens.

from fleet-telemetry.