Just wanted to check if there was any progress with embedded, multi-tenant n8n? Or is there some estimation when it will be developed?
Just as @sbilde described, I also look to provide some kind of in-app app-integrations.
All the other solutions are super expensive and probably way too much for what I need.
Happy to provide some context here. The team is currently developing a user management feature - this would allow multiple users to co-exist on a single instance together. This feature will be rolled out in phases:
Phase 1 - basic user management; we plan to have a flag that disables sharing between users and so essentially users would only see their own workflows and credentials. This should enable various embed cases where team functionality is not required (i.e. multiple user co-existing on one “account”).
Phase 2 - we expect to roll out workspaces functionality. It’s designed with embed users in mind, so this would allow for 1 SaaS account to have multiple users on an instance (i.e. a LOB or team could be supported). We will have a few configurable permissions that essentially allow for a SaaS model to be implemented. Since n8n can be setup with a redis database and n number of workers, this along with workspaces should enable many SaaS embed usecases.
Generally, the auth system for user management is being built with embed users in mind (programatic provisioning of user accounts etc.).
Beyond user management, we do have more sophisticated multi-tenancy on our roadmap (i.e. for very large scale deployments) but we don’t expect to break ground on this during this quarter. So unless you’re dealing with very stringent data isolation requirements (i.e. HIPAA customers), or very large scale - user management phase 1 or 2 should unblock you realising your usecase.
Hope that helps - It would be great to know your requirements for auth/ multi-tenancy, and details like # of users you’d like to support. Feel free to DM me with any project specifics!
I use n8n in Docker.
Is it possible to use it with combination of nginx as a reverse proxy with a third-party authentication provider?
For a new registered user a new docker container is spawned, each existing user is logged in into his/her own container. New containers are generated from the latest image that is stored on the server, for example. Each container can have a restart option enabled to minimize downtime if something goes wrong.
There are several other question regarding administration of each docker, how to conveniently update each container etc. I don’t have experience to estimate if it’s hard to do or not.
Another vote for this functionality. It’s a minimum requirement for our use-case.
If we are embedding n8n directly inside our application, can we programmatically log the user in via stored credentials so that they don’t have to log in to our application, and then again into n8n?