Here is my setup:
public class ApplicationUser : IdentityUser
{
}
public class ApplicationRole : IdentityRole
{
}
public class Applic
I am now on ASP.NET Core 1.1 and this behavior has been fixed.
I can easily implement my own UserManager and UserStore, then bootstrap the app as following:
// identity models
services
.AddIdentity()
.AddEntityFrameworkStores()
.AddUserManager()
.AddUserStore()
.AddDefaultTokenProviders();
and inject both UserManager and UserStore into my Controller, without any problem:
public AccountController(
IIdentityServerInteractionService interaction,
IClientStore clientStore,
IHttpContextAccessor httpContextAccessor,
ApplicationUserManager userManager,
SignInManager signInManager,
IEmailSender emailSender,
ISmsSender smsSender,
ILoggerFactory loggerFactory)
{
_interaction = interaction;
_userManager = userManager;
_signInManager = signInManager;
_emailSender = emailSender;
_smsSender = smsSender;
_logger = loggerFactory.CreateLogger();
_account = new AccountService(_interaction, httpContextAccessor, clientStore);
}