[Feature Request]

[DavidHill0809]

Is your feature request related to a problem? Please describe.
No it is just an addition to the Authorisation scheme in the device config.

Describe the solution you'd like
We have a huge number of devices to configure on TBMQ and would like to create common Authorisation maps per device group. Would it be possible to make "Device Profiles" like Thingsboard does?

Describe alternatives you've considered
Creating individual configurations but this will not scale well if changes need to be made with large numbers of devices.

Additional context
N/A

[dmytro-landiak]

hi @DavidHill0809,

so basically you would like to have the possibility to configure matcher regex for Intermediate certificate CN (instead of client's certificate CN) that is common for the specific device group as shown in the screenshot below?

Did I understand your request correctly?

I assume you can not use some client certificate CN matcher regex that would be applied for many devices from the same group?

[DavidHill0809]

Hi Dima, No, I don't think that is what I am asking. Let me try to explain a bit better: * We have a few different types of gateways that we install on sites. For example we use Inala gateway, Teltonika RUT955, Techbase NPE-X500. * We have around 1000 Teltonika's at present which are connected to large power systems and collect data from a lot of MQTT sensors. * We have around 1000 Techbase NPE-X500 which also connect to a lot of equipment on Telecoms towers which we monitor. * We are starting to use Inala boxes for the Telecoms tower monitoring. * These gateways publish to the MQTT broker using standard topics based on their configuration version, so: * Teltonika will publish to <CUSTOMER_NAME>/<COUNTRY>/<DEVICE_IDENTIFIER e.g. EM4X_NEC_0401>/<SITE NUMBER> * Lots of sites are publishing like this and we use <CUSTOMER_NAME>/<COUNTRY>/<DEVICE_IDENTIFIER e.g. EM4X_NEC_0401>/+ on Thingsboard for Integration * Techbase will publish to <CUSTOMER_NAME>/<COUNTRY>/<DEVICE_IDENTIFIER e.g. TB_NEC_4302>/<SITE NUMBER> * We do the same on Thingsboard to listen on a wildcard for the site_name * TBMQ allows the device configurations to create regex based authorisations per device which can limit the topics published to, which for us is a great feature. * Problem is that we will need to configure the regex for each device individually and if we make a change then we need to apply to each of the 1000 devices individually * Would be really awesome if there was a concept of device profile (like Thingsboard) which contains the regex map for authorisation and instead of configuring the authorisations per device you rather attach a device profile. I hope this explains better. Regards, David From: Dima Landiak ***@***.***> Sent: Thursday, July 27, 2023 9:32 AM To: thingsboard/tbmq ***@***.***> Cc: David Hill ***@***.***>; Mention ***@***.***> Subject: Re: [thingsboard/tbmq] [Feature Request] (Issue #55) Caution: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know that the content is safe. Use the "Report Phishing" button if you suspect the email is suspicious. hi @DavidHill0809<https://github.com/DavidHill0809>, so basically you would like to have the possibility to configure matcher regex for Intermediate certificate CN (instead of client's certificate CN) that is common for the specific device group as shown in the screenshot below? [image]<https://user-images.githubusercontent.com/10978307/256460348-fcc9e6e7-db91-4968-a387-865d4f2a8804.png> - Reply to this email directly, view it on GitHub<#55 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AR3RMSF74GGCKHGY5WG742TXSIKOJANCNFSM6AAAAAA2ZTO2S4>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[dmytro-landiak]

Thank you for the explanation, I will get back here once we have more information for you regarding the request.