Share your application service please
You can use Object Extensions to extend IdentityUser . You can also persist it via mapping to database column.
Try dotnet build /graphBuild in your main microservice solution directory. That should build all related projects. Preferably after deleting bin&obj folders (there should be a delete-bin-obj-folders.bat file under main solution directory as shortcut).
AdministrationService is having problems with finding OrderServiceApplicationContractsModule.
Try building OrderService.
Note: The Microsoft.EntityFrameworkCore.Tools package was recently upgraded to 5.0.8 which seemed to cause version conflicts with 5.0.7 during the build. I worked around the issue by downgrading to 5.0.7 and editing any .csproj files that contained version 5.0.* and replaced them with 5.0.7 explicitly.
This is about local nuget cache missmatch with Microsoft.EntityFrameworkCore. You can also try removing <PrivateAssets>all</PrivateAssets> line.
Solutions to this problem will be a local solution.
We will discuss about using specific version of Microsoft.EntityFrameworkCore.
User permissions are requested by AdministrationService (permission management) from IdentityService (IdentityUserAppService) behind the scenes.
So, when you try to get the list of permissions of a user (Identity Management-> User Management -> Permission action), this internal communication happens.
Does the internal gateway play a role at all in the microservice template? Thanks!
Yes, big time. It is the gateway and locator for other microservices when you try sync-communications (http) between microservices.
Default template uses it for communication betweeen AdministrationService and IdentityService for user permissions as i have mentioned above.
I will fix missing points in documentation about this, thank you.
For external applications we created the API client credentials and we are able to do API calls.
Since you are making external calls, there is no default handling for it. Base way is to add tenantId to requests headers manually as you have mentioned.
They are project references so you will need to build them first. Or do a graphBuild on your main solution with dotnet build /graphBuild.
Share the js code where you create the datatable please.
Try setting AccessTokenLifetime (or also IdentityTokenLifetime if you need) to 15*60 (token values are in seconds).
If you are using hybrid/authorization code flow and using refresh token; also set AbsoluteRefreshTokenLifetime to 15*60.
We have updated AbsoluteRefreshTokenLifetime, AccessTokenLifetime, IdentityTokenLifetime for 60*5 seconds for testing. But the application logs out forcefully even if the user is active. This is one of the important task we are looking to implement ASAP. We will appreciate your quick response.
I couldn't understand your scenario. If you set AbsoluteRefreshTokenLifetime to 60*5, it will absolutely log you out after 5 mins. Keep this time longer and keep your Access and Identity tokens life time shorter so that, if the access token is compromised, it will be refreshed in short amount of time.
This is not related with ABP, you can check identity server docs for more information