Can the MQTT user password be something other than the Device Token?

TagoIO Devices and Connectors
1

I have a Milesight device that I would like to connect to Tago to send data via MQTT.

However, the device has a limit on the number of characters that can be input into the password field and the Device token does not fit.

Is there an alternative way of setting user name and password required for the connection?

2

What I do is to have a general MQTT broker on my server, which will be recieving info from your end nodes. Then you can forward all the topics you want to Tago MQTT, where you can set the connection to a general handler device, and then route each message to the real device in Tago.

Its a bit cumbersome but it really works.

3

Hi Milica and Ischacht,

That is definitely a valid way to circumvent this issue.

This post might also help on understanding how to split the received data to your multiple devices.

4

I have a very similar problem: I have a SeeedSense Device (SenseCAP 4G) that I would like to connect to Tago to send data via MQTT.

However,
the device has a 32 byte limit on the number of characters that can be input
into the password field and the device token generated by Tago.io is 36 bytes, which is too long.

@Freddy Minuzzi, your response above “That is definitely a valid way to circumvent this issue.” suggests there may be other workarounds. Although I can use my own broker on my server as an intermediate, this is exactly the sort of kludge I am moving to Tago to avoid - are there any other options?

5

Hi Intuitiologist,

We have good news!

We are also currently investigating the possibility of creating custom tokens through the use of profile ids in conjunction with network ids. This would necessitate the modification of the API URL.

Currently, we don’t have a date yet but we intend to have this completed soon.

6

Hello @Freddy Minuzzi,

Are there any news regarding the possibility of creating custom tokens to use as MQTT passwords?

Thanks in advance!

7

Hello, any news on this? I have the same issue with a thingslog datalogger

8

What happened to this? Did the idea go dead? We also have devices with 30 character password limits.

9

Hello @iot1

TagoIO’s public MQTT broker authenticates with Device Tokens as passwords, and we don’t have a near-term plan to change that on the public broker.

If your device cannot accommodate the token length, a practical workaround is to deploy a dedicated MQTT broker via TagoDeploy. This gives you a standalone broker connected to your TagoIO account where you can:

  • Define your own username/password format (shorter credentials supported).
  • Optionally use client certificates.
  • Manage credentials according to your security policies.

We’re also working on two enhancements:

  • An Restful API to programmatically manage credentials and automate provisioning.
  • An option to sync Device Tokens with your TagoIO profile as credentials, if you prefer to align with the current public-broker model.
1 Like