Dynamic Authorization/Deauthorization

[bonastreyair]

Hi!

Is there a way to dynamically authorise/deauthorise users from the configuration node of a TelegramBot or it is just static configuration that can only be modified manually?

I tried to add {{context.global.authorised_telegram_users}} (which is a list of the usernames that I set before in the Node-RED global context) but I can't make it work...

If there is no way to do it right now, I think it would be awesome to add this functionality.
I'm using version 7.1.1 in Node-RED 1.0.3.

Thanks!

[windkh]

Hi @bonastreyair right now this configuration is a static one. I can add this dynamic thing if you want to, but I don‘t really understand the use case behind that. Can you give me a little hint ?

[bonastreyair]

Hi, thanks for your quick response!

Imagine you create an aplication for a little company, they want to be able to add or revoke the authorised users to have access to the commands (for checking the temperature in a room for example) but you can't let them modify the Node-RED application.

So I think (for example) sending a configuration email (or whatever other comunication mean), recieved in Node-RED and treated in a way, so that automatically changes the Telegram configuration node to add or remove a "user_name" from the authorised list. Doing so the little company could handle the authorisation of the access of the commands without entering the Node-RED application. In this case I understand that Node-RED should catch the new configuration without the need to "redeploy" anything.

I hope I could explain the "case" I have in mind. What do you think? :)

Thanks!

[windkh]

That is understood. I wonder how that can be implemented... give me some hours to rethink that. Thanks for providing that idea...

[Swiftnesses]

This sounds awesome, would love to see it implemented ;-)

[windkh]

version 7.2.0 support that feature

[windkh]

hope it works guys

[bonastreyair]

I will check it out as soon as I can! You are awesome! Thanks!

[windkh]

de nada