We recently migrated from v7.2 (standard) to v7.3 commercial, and at the same time from Identity Server to OpenIddict.
We use the following to provide our own SignInManager and UserManager for the purpose of responding to various login steps:
PreConfigure<IdentityBuilder>(identityBuilder =>
{
identityBuilder.AddRoleManager<VpxRoleManager>();
identityBuilder.AddSignInManager<VpxSignInManager>();
identityBuilder.AddUserManager<VpxUserManager>();
});
It looks like UserManager.FindByNameAsync is no longer called, or no longer called for every login attempt. We've been hooking that function to perform as-needed synchronisation of user account details from an external source.
Are we missing a configuration step or has the workflow changed and we should be hooking a different function now?
- ABP Framework version: v7.3.0
- UI type: Angular
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
4 Answer(s)
-
0
hi
You can try to replace the
AbpSignInManagerandIdentityUserManagerandIdentityRoleManager.https://docs.abp.io/en/abp/latest/Customizing-Application-Modules-Overriding-Services
-
0
hi
You can try to replace the
AbpSignInManagerandIdentityUserManagerandIdentityRoleManager.https://docs.abp.io/en/abp/latest/Customizing-Application-Modules-Overriding-Services
Doesn't this already replace the IdentityUserManager with our own?
identityBuilder.AddUserManager<VpxUserManager>();Our logs show our user manager IS getting called by Abp, just no longer the FindByNameAsync method.
-
1
hi
Some services are injected the
Volo.Abp.Identity.IdentityUserManagerso your own will not work. -
0
Thankyou, that worked!
