Implementing Multi User And Multi Tenant Management In Node Red I'm working on a project where i need to implement multi user and multi tenant management in a node red dashboard. the challenge is that i want to achieve this without enabling flow fuse user authentication or relying on any external authentication mechanisms. We have two fundamental design patterns when building a dashboard: single source of truth: all users of your dashboard will see the same data. this is useful for industrial iot or home automation applications. multi tenancy: data shown in a particular widget is unique to a given client session user.
Implementing Multi User And Multi Tenant Management In Node Red In this video, we explore how to create both single source of truth and multi tenancy dashboards in node red. A collection of containers and definition files that will implement a multi tenant node red environment on kubernetes. I'm working on a project using node red deployed on the kubernetes platform (eks), with data volume mounted to efs and ingress load balancing configured. we are setting up version control for the node red flows using bitbucket. It actually isn't really hard to create a multi user setup using multiple node red instances if you need separate flows for each user. the sensible approach is to either use docker or just individual instances (since node red is simply a node.js app, this is easy) behind a reverse proxy.
Implementing Multi User And Multi Tenant Management In Node Red I'm working on a project using node red deployed on the kubernetes platform (eks), with data volume mounted to efs and ingress load balancing configured. we are setting up version control for the node red flows using bitbucket. It actually isn't really hard to create a multi user setup using multiple node red instances if you need separate flows for each user. the sensible approach is to either use docker or just individual instances (since node red is simply a node.js app, this is easy) behind a reverse proxy. Over the month of october i'll be releasing a series of blog posts outlining all the components needed to build such a system and finally how to assemble them into a proof of concept deployment. the first post is now live here. Over the course of october i will be publishing a series of blog posts outlining how to build a multi tenant (multi user) node red service. you will be able to follow the posts here:. On balance, it hasn't been considered worth the disruption and effort when there are other viable options such as providing a runtime per user and managing the orchestration of those runtimes outside of the core of node red. Dashboard 2.0 has recently added multi tenant capabilities and support that i want to share with you. and i am also working on a simple dashboard user logon solution for some simple user.
Comments are closed.