Agent does not forward gateway id to sdk during device activation/update
Closed this issue · 4 comments
Can you give some more details on what problem this causes? Is it just that the agent and frontend go out of sync if the gateway id gets updated on the agent or something else?
Now that we have the gateway id in device tokens for authentication purposes (Sparkplug etc.), if a device is registered for the first time with an explicit gateway id, then frontend does not receive it and by default it assigns device id as the gateway id. This is not exactly an issue with the agent, sdk does not support this as well, so first sdk needs to be fixed, I have opened the related issue there. I also believe the current device information update mechanism does not check if the gateway id is changed, which needs further investigation. I am working on the fix for the sdk, once it is done, I will update the agent too.
TLDR: Frontend and agent goes out of sync, which causes authentication problems.
I think this got fixed right @oguzcankirmemis ?
Yeah, it did, closing...