ABP Commercial 9.1.0 / Blazor Server / EF / Non tiered / Separate Host and Tenant DBs / Lepton Theme
Hi we are attempting to create a v7.4.2 newly templated solution so that we can compare it to version 9.1.0 and make necessary adjustments after a ABP upgrade.
The issue we are having is that we cannot seem to specify the Lepton theme in the abp new command, no matter what theme we specify, the solution gets created with the leptonxlite theme.
Our current production application uses the Lepton theme (not LeptonX or LeptonXLite). We have many custom css overrides based on the Lepton theme, so upgrading to LeptonX is not an option right now.
The command we are issuing is...
abp new ABPTemplate742 -t app -u blazor-server -d ef --theme lepton --mobile none -v 7.4.2
Please advise. Thank you in advance.
Thank you for your help maliming.
Once I cleared my cookies everything worked as expected.
Hi,
I was able to get the template solution to work and found that I could not replicate the two factor issue. So it is unclear to me why we are seeing the issue in our solution.
To debug, I overrode GetTwoFactorEnabledAsync in the IdentityProUserStore and found that when it runs, it correctly returns true because the tenant's 2fa setting is set to forced.
Our override to the login process relative to 2fa is not changed from the original ABP implementation...
var result = await SignInManager.PasswordSignInAsync(
LoginInput.UserNameOrEmailAddress,
LoginInput.Password,
LoginInput.RememberMe,
true
);
await IdentitySecurityLogManager.SaveAsync(new IdentitySecurityLogContext
{
Identity = IdentitySecurityLogIdentityConsts.Identity,
Action = result.ToIdentitySecurityLogAction(),
UserName = LoginInput.UserNameOrEmailAddress
});
if (result.RequiresTwoFactor)
{
return RedirectToPage("./SendSecurityCode", new {
returnUrl = ReturnUrl,
returnUrlHash = ReturnUrlHash,
rememberMe = LoginInput.RememberMe,
linkUserId = LinkUserId,
linkTenantId = LinkTenantId,
linkToken = LinkToken
});
}
result.RequiresTwoFactor returned from await SignInManager.PasswordSignInAsync returns false.
Hi
I emailed you a link to the project solution.
I used abp suite to create the application it is using Lepton theme at version 7.2.1. I ran install-libs from the ProjectName.Blazor folder.
{
"version": "1.0.0",
"name": "my-app",
"private": true,
"dependencies": {
"@volo/abp.aspnetcore.components.server.leptontheme": "7.2.1",
"@volo/abp.aspnetcore.mvc.ui.theme.lepton": "7.2.1",
"@volo/account": "~7.2.1",
"@volo/cms-kit-pro.admin": "~7.2.1",
"@volo/language-management": "~7.2.1"
}
}
I'm trying to create a new project from the template and I'm getting the following when clicking on the login link.. I already ran yarn and abp install-libs from the solution folder.
An unhandled exception occurred while processing the request. AbpException: Could not find the bundle file '/libs/bootstrap/js/bootstrap.enable.tooltips.everywhere.js' for the bundle 'Lepton.Global'! Volo.Abp.AspNetCore.Mvc.UI.Bundling.TagHelpers.AbpTagHelperResourceService.ProcessAsync(ViewContext viewContext, TagHelper tagHelper, TagHelperContext context, TagHelperOutput output, List<BundleTagHelperItem> bundleItems, string bundleName)
Yes, every user has a confirmed email, but 2fa isn't enforced because its turned off at the user level.
in our system all users self-register and when the tenant is set to have 2fa Forced, all newly registered users get created with 2fa turned off, so in essence 2fa is never forced. so this means an admin has to manually visit each user to turn on 2fa?
Additionally, in our system all users will always have a verified email for use in 2fa.
Thanks.
If I change the tenant's 2FA setting to 'Forced', the user cannot turn on/off their 2FA under their profile which makes sense. but if the user had 2FA turned off on their profile and the tenant setting is now set to 'Forced', shouldn't the user have to perform 2fa to login in? This user has a 2fa provider setup for email.
In order to make this work, we had to set the tenant 2FA setting back to 'Optional' then turn on 2FA for the user, then set the tenant back to 'Forced'
Is there something we are missing here? shouldn't all users be required to do 2fa if it is setup as 'Forced' on the tenant level (regardless of what the setting is on the user level)?
