I've a microservice application (7.4.5) with:
- Identity
- Saas
- Administrative
- Crm
Now I want to add a new application ERP (abp 9.1.3). If I create a new solution
- Identity
- Saas
- Administrative/Administration
- audit-logging
- gdpr
- language
- ERP
My customer start using Crm application and now ask to add ERP service. Erp and Crm are complete different application with separate UI, differente permissione and other stuff the only connection is single user and tenant.
I need to use same ABP version I suppose. I create a path to upgrade current module from 7.4.5 to 9.1.3 but how can I get a single user and tenant but different permission, localize data and logs?
Is it possible?
5 Answer(s)
-
0
To achieve a shared user and tenant base across multiple ABP microservice applications (such as CRM and ERP), while keeping permissions, localization, and audit logs separate per application, you should:
Upgrade all your services and modules to the same ABP version (e.g., 9.1.3). This is required for compatibility, especially for shared modules like Identity and Saas.
Use a shared Identity and Tenant Management service:
- Both CRM and ERP applications should use the same Identity and Saas microservices for authentication and tenant resolution.
- This ensures users and tenants are managed centrally and are accessible from both applications.
Isolate permissions, localization, and audit logs:
- Each application (CRM, ERP) can define its own permissions, roles, and policies. ABP's permission system is modular and supports per-application configuration.
- Localization resources can be separated by module or application, so each app can have its own translations.
- Audit logging is also modular; each service can log its own actions independently.
UI and API separation:
- Each application can have its own UI and API, with separate permission sets and features, but still rely on the central Identity and Tenant Management.
Multi-tenancy:
- ABP's multi-tenancy system ensures that all data is tenant-scoped, and users are associated with tenants, regardless of which application they use.
This architecture is fully supported by ABP. You only need to ensure all services use the same Identity and Saas backends, and that all modules are upgraded to the same ABP version.
Sources:
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
-
0
And about auth server I need to have one ore more auth server?
-
0
hi
You need to use the same version of the ABP package and use the old CLI to create the new microservice template project.
Thanks.
-
0
Ok.
I understand that version must be the same but about auth server I need to create a separate server? Are there other operation to do do?
-
0
hi
The previous solution has an AuthServer project.
Can you share a screenshot of your solution (
microservice application (7.4.5)) structure?Thanks
