Register new user under different Tenant (Tenant impersonation)

My application is built using .NET Core 3.1 with Finbuckle.MultiTenant.AspNetCore 6.0.0.

As the super administrator, I want to create an administrator for another new tenant. Note that

1. I am able to set tenant using TrySetTenantInfo()
2. However when I register a new user, the user is registered under my current logged in tenant. So in the AspNetUsers table, the Tenant Id of the new user is the Id of the tenant I am logged in with.

Please can someone point me in the right direction?

My code is:

           //Correctly gets the current tenant
            var currentTenant = HttpContext.GetMultiTenantContext<ApplicationTenantInfo>()?.TenantInfo;
            
            //Correctly retrieves the target tenant
            var targetTenant = _store.TryGetAsync(model.TenantId.ToString()).Result;

            //Correctly sets the new tenant to the target tenant
            bool isSet = HttpContext.TrySetTenantInfo(targetTenant, true);

            //Verify that target tenant is correctly set, works
            var newTenant = HttpContext.GetMultiTenantContext<ApplicationTenantInfo>()?.TenantInfo;       

            if (ModelState.IsValid)
            {
                var password = RandomGenerator.GenerateRandomString(8);
                var user = new ApplicationUser { UserName = model.Email, Email = model.Email, Name = model.Name, PhoneNumber = model.PhoneNumber };                
                
                //User is not created using the target tenant
                var result = await _userManager.CreateAsync(user, password);
                //bool reset = HttpContext.TrySetTenantInfo(currentTenant, false);
            }

            var tenants = _store.GetAllAsync().Result;
            ViewBag.TenantId = new SelectList(tenants, "Id", "Identifier");
            return View(model);
        }

I have also tried:

var accessor = _serviceProvider.GetRequiredService<IMultiTenantContextAccessor>();
            var multiTenantContext = new MultiTenantContext<ApplicationTenantInfo>();
            multiTenantContext.TenantInfo = newTenant;
            accessor.MultiTenantContext = multiTenantContext;

[AndrewTriesToCode]

@coommark I think I’ve got it and if I’m right you might want to kick yourself (I say that as someone who does this to my self frequently):

In your first attempt above:

            bool isSet = HttpContext.TrySetTenantInfo(targetTenant, true);

            //Try re-resolving the user manager from DI as per @AndrewTriesToCode          
            var userManager = HttpContext.RequestServices.GetService<UserManager<ApplicationUser>>();
            
            if (ModelState.IsValid)
            {
                var password = RandomGenerator.GenerateRandomString(8);
                var user = new ApplicationUser { UserName = model.Email, Email = model.Email, Name = model.Name, PhoneNumber = model.PhoneNumber };                
                
                
                if(result.Succeeded)
                {
                    //Send email with password, tenant name, login link                    
                }

                bool reset = HttpContext.TrySetTenantInfo(currentTenant, true);
            }

Note that this line is not using the newly resolved userManager but instead the original _userManager:

//User is not created using the target tenant
var result = await _userManager.CreateAsync(user, password);

Let me know how it goes!

[AndrewTriesToCode]

Hi ok I’ll start digging in. Do you have a simple project or repo that shows the problem you can share with me?