Using MQTT "API" for setting DyncSec

[OpoOpo]

It would be nice to use BunkerM as an MQTT Client with admin rights, so the BunkerM would not need to reach the dynamic-security.json file.
Yes, it would need to run in different "mode" in the sense that, for example, enabling anonymous clients could not be possible.
https://github.com/eclipse-mosquitto/mosquitto/tree/master/plugins/dynamic-security

[bunkeriot]

@OpoOpo BunkerM’s backend API currently uses admin rights to add new Dynamic Security ACLs. It only interacts with dynamic-security.json file when importing mosquitto_passwd files. With some tweaks, it integrates these files into Dynamic Security, even though Mosquitto’s password system works completely differently.

[OpoOpo]

I saw it and I am trying to propose not to modify the dynamic-security.jsondirectly but through MQTT API so that BunkerM does not need to interact with mosquitto files.

[bunkeriot]

@OpoOpo You're probably right—I should stick to using Dynsec APIs everywhere. The only downside is that there's no way to add multiple users in batch, so adding 100 users would require 100 API calls. Still, I’ll give it a try to see if it’s performant enough

[OpoOpo]

Based on the JSON structure, it should be possible to send multiple create user commands in one request because the JSON has a commands [] array.