search

authorizerdev / authorizer

Your data, your control. Fully open source, authentication and authorization. No lock-ins. Deployment in Railway in 120 seconds || Spin a docker image as a micro-service in your infra. Built in login page and Admin panel out of the box.
https://authorizer.dev
MIT License
1.59k stars 162 forks source link

Assign user to multiple application/clients #387

Open yescine opened 1 year ago

yescine commented 1 year ago

Feature Description Similar to FusionAuth and Keycloak user can have multiple registration in different apps or clients

Describe the solution you'd like Create an entities in which the we assign appropriate user to it.

Describe alternatives you've considered The alternative is to add some metadata (companyId, appName...) in the "app_data" field in user schema, it make it hard to filter and process users from the one API call

Additional context Not to confuse with multitenancy (or what Keycloak call Realm), make Authorizer the central authentication microservices

lakhansamani commented 1 year ago

Authorizer does set a global subdomain cookie, so ideally it should be feasible to set authorizer as a central authentication microservice, it is better to add a field called tenant for multi-tenancy?

yescine commented 1 year ago

@lakhansamani this would work for now (with extra work filtering data to access the right tenant).