Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Invalid Kuksa jwt tokens for Databroker

Not a Bug

Description

I am working on adding support for Databroker to the control panel.

This bug was found while using the latest Qt IVI build, where kuksa-val-server has been replaced by Databroker. 

Steps to recreate the issue:

  1. Launch the Databroker in Qt IVI image with the following command:

  1. Connect to the Databroker via cli with the following command
    Note: CA.pem used for ca-certificate 

  1. The connection was established successfully in secure mode.

  2. I tried to authorize the client with the following command: 

 
However, I got the following error:

I have verified the same by running similar steps using the client on the AGL image, modifying the control panel's config.py file and also using other available tokens. 

Environment

None

Activity

Show:

Scott Murray 
October 2, 2023 at 6:23 PM

As explained via email, the issue is that the KUKSA.val databroker uses a different authorization token format than the older server.  I believe you've resolved the issue with a switch to an appropriate token, if not please reopen.

Details

Assignee

Reporter

Components

Priority

Created September 28, 2023 at 3:39 PM
Updated October 13, 2023 at 8:07 PM
Resolved October 2, 2023 at 6:23 PM