Open-source, scalable, and fault-tolerant MQTT broker able to handle 4M+ concurrent client connections, supporting at least 3M messages per second throughput per single cluster node with low latency delivery. The cluster mode supports more than 100M concurrently connected clients.
Currently, in 1.3.0, the Sessions tab shows, quite obviously, a list of sessions. This is extremely useful and helps with debugging and maintenance an awful lot.
I would like that tab to show which Credentials are used for that session (using the name of the credentials as shown in the Credentials tab).
I have got a LOT of legacy devices that have been migrated from company to company, from customer to customer, and ended up in my broker using very outdated and insecure credentials. I would love to be able to see which ones are using those deprecated credentials in the sessions view.
Thank you for the request. This is a very valid and useful feature, and we have already planned to implement this in the upcoming releases. Please, stay tuned for the updates.
Currently, in 1.3.0, the Sessions tab shows, quite obviously, a list of sessions. This is extremely useful and helps with debugging and maintenance an awful lot.
I would like that tab to show which Credentials are used for that session (using the name of the credentials as shown in the Credentials tab).
I have got a LOT of legacy devices that have been migrated from company to company, from customer to customer, and ended up in my broker using very outdated and insecure credentials. I would love to be able to see which ones are using those deprecated credentials in the sessions view.
This is an example of what I would love to see :
Those credentials names would be taken from :
Thank you very much !