You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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?
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
The text was updated successfully, but these errors were encountered: