Closed gaizkasi closed 4 months ago
Hi @gaizkasi!
Thank you for your question. Could you please provide more details about the dynamic client credentials provisioning you aim to achieve?
Currently, if authentication is enabled on the broker, client credentials need to be pre-created to allow devices to connect. Automatic creation of credentials during device connection is not supported.
However, you can use our API to provision client credentials before the device attempts to connect, bypassing the need for the UI.
If you can provide additional details about your specific use case, I would be glad to assist further.
Regards!
Hi @dmytro-landiak!
I mean, what I would like to have is a process in TBMQ as in the standard Thingsboard Transport where you could provide using RPC request/responses the credentials for a device:
https://thingsboard.io/docs/user-guide/device-provisioning/?mqttprovisioning=x509-certificate
I don't know if the API that you mention does something similar. Is that in the documentation?
Regards!
Gaizka
hi @gaizkasi!
Thank you for your inquiry regarding the Device Provisioning feature. Currently, this feature is available in TB but not in TBMQ.
We understand the importance of this functionality and will consider adding it to TBMQ in future updates. However, please note that it is not on our current roadmap, so it won't be included in the immediate upcoming releases.
If you have any further questions or need assistance with other features, please feel free to reach out.
Regards!
Thanks for all!
Component
Description I would like to deploy MQTTS in TBMQ publications and I would like to know how I could manage MQTTS credentials configuration taking into account that device provisioning must be dynamic, that is, not using UI.