Multi tenants for one application
-
Hello, there's something I can't understand with the tenants, a priori when we create an application we have to provide it with a single tenant.
So I'm wondering what's the point of passing a tenantId in the authorization url? Since apparently it doesn't take into account the tenant passed and systematically uses the tenant linked to the application.
As a result, I can't quite grasp the usefulness of the tenants. Could you clarify this for me?
Thank you
-
@vandaele-seba A tenant in FusionAuth is a named object that represents a discrete namespace for Users, Applications, and Groups. It is a way to separate Users, Applications, and Registrations into separate containers. There is a diagram in the documentation that may help.
-
@vandaele-seba @mark-robustelli
I agree that it seems non-intuitive. I'm building a B2B2C multi-tenant application; it's very awkward trying to shoehorn things in the other way around.In my case, we have user accounts that can exist in, and have different permissions to, different tenant instances of the same application. I'm planning to work around this by using API to creating a new instance of the application from a sort of hard-coded template every time I create a tenant, and creating duplicates of users in the same fashion. But it's certainly awkward, I wish there were a way to share Applications and Users across tenants.
OR, perhaps a new concept is needed in FusionAuth -- "Organizations" if you will -- that allows for granting users with different permission sets inside the same Application.
-
