Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assign user to multiple application/clients #387

Open
yescine opened this issue Aug 25, 2023 · 2 comments
Open

Assign user to multiple application/clients #387

yescine opened this issue Aug 25, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@yescine
Copy link

yescine commented Aug 25, 2023

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

@yescine yescine added the enhancement New feature or request label Aug 25, 2023
@lakhansamani
Copy link
Contributor

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
Copy link
Author

yescine commented Aug 26, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants