We fixed it, it was a problem with multitenancy.
The Identity.TwoFactorUserId cookie is included as seen here
We've implemented our own login controller for use by an external app.
The login endpoint uses the signinmanager:
protected SignInManager<Volo.Abp.Identity.IdentityUser> SignInManager { get; }
And logs in:
var signInResult = await SignInManager.PasswordSignInAsync(
login.UserNameOrEmailAddress,
login.Password,
login.RememberMe,
true
);
This works fine for users without 2-factor enabled.
When 2-factor is enabled, we get the expected 2-factor cookie back:
Which we then provide in the header when calling a SendSmsSecurityCode endpoint.
This it where we get confused: SignInManager.GetTwoFactorAuthenticationUserAsync() returns null. How can this happen? Are we doing something wrong?
Alright, but if we'd like to modify the source for this, which module should we download the source for?
When expanding and minimizing categories in the menu by pressing the little arrow, the buttons appear with an animation.
When expanding, the buttons are animated from top to bottom, but when minimizing they move from right to left.
How and where in the source can we modify this behaviour? We'd like the minimizing to move from bottom to top.
Thank you, I think we can solve it now :)
We would like to simplify the login process, by removing the need to specify tenant. Users will have to be unique across tenants, and the system will choose the tenant based on the username entered during login.
Can we get some pointers on how to achieve this functionality?
Thank you.
Does 3.1.1 only contain changes to the discussed bug? Do you post release notes somewhere?
We are getting the same bug in 3.1.0 that was reported in version 3.0.3 by thanhvl1@fsoft.com.vn:
Steps to reproduce:
Pressing save and generate fails.
We tried using just the "AuditedEntity" instead of "FullAuditedEntity" and this works correctly.