Description
Is there an existing issue for this?
- I have searched the existing issues
Description
I am currently working on an Angular application integrated with the ABP Framework and Entity Framework Core. After upgrading the backend from .NET Core 6 to .NET Core 8, I have encountered an issue where I am unable to retrieve the CurrentTenant.Id in my API endpoints.
Reproduction Steps
- Upgrade the backend from .NET Core 6 to .NET Core 8.
- LogIn to the Angular application.
- Attempt to access an API endpoint that requires the CurrentTenant.Id.
- Observe that the CurrentTenant.Id is always null.
Expected behavior
After user login, the CurrentTenant.Id should be populated correctly in the API endpoints, as it was before the upgrade.
Actual behavior
The CurrentTenant.Id is always null when attempting to access API endpoints after upgrading to .NET Core 8.
Regression?
No response
Known Workarounds
- This issue occurs specifically after upgrading from .NET Core 6 to .NET Core 8.
- The issue is observed when accessing API endpoints from the Angular application.
- Interestingly, when sending requests using Postman, the CurrentTenant.Id is correctly populated, indicating that the issue might be related to the interaction between the Angular application and the .NET Core 8 backend.
Version
8
User Interface
Angular
Database Provider
EF Core (Default)
Tiered or separate authentication server
None (Default)
Operation System
Windows (Default)
Other information
I have tested the API endpoints using Postman, and the CurrentTenant.Id is correctly populated, indicating that the issue might be specific to the interaction between the Angular application and the .NET Core 8 backend.