A follow up question....
In the authenticator app, the application is identified using the .NET project name <company>.<app>.Blazor, How can we customize the application name registered with the user's authenticator app?
Thanks @maliming!
I forgot about install-libs, that worked :-)
Hi @mailiming,
{
"version": "1.0.0",
"name": "my-app",
"private": true,
"dependencies": {
"@volo/abp.aspnetcore.mvc.ui.theme.lepton": "~7.4.2",
"@volo/abp.aspnetcore.components.server.leptontheme": "~7.4.2",
"@volo/cms-kit-pro.admin": "~7.4.2",
"@volo/account": "~7.4.2"
}
}
Hi @liangshiwei,
We don't recall noticing the issue when we were on versions 5 and 6, but after doing some debugging on our end, I'm thinking this may have been a problem back then as well and we just didn't notice it because our initial screen after logging in back then was less complex and we were not running in a hosted environment (local dev only).
ABP Commercial 7.2.1 / Blazor Server / EF / Non tiered / Separate Host and Tenant DBs / Lepton Theme
Hi @liangshiwei,
I replicated the issue with a newly templated solution using the ABP CLI (see screenshot below)
abp new ABP.Test -u blazor-server -v 7.2.1 -theme lepton
In local development with a simple ABP page, the problem almost can't be perceived because everything is running fast. The problem is magnified when a page has a lot to it. The problem is additionally magnified when being run from a hosted solution that is slower than in local development.
The problem seems to be isolated to the menu tree on the left where css styling applies after the content is loaded.
It's only an issue on the initial load of the application or on a browser level refresh. Navigating to different pages from the menu does not cause a problem.
Our application loads a significant dashboard once logged in and that's why the issue is more apparent to us, especially when running from a hosted solution on the internet.
I disabled caching in the browser's developer tools to be able to better see the problem for a screeenshot.
Any insight, suggestions, or workarounds would be greatly appreciated. Thanks.
Hi @liangshiwei,
We are on ABP 7.2.1 Blazor Server (Lepton) and this issue has been a big issue for us as well. We are not on LeptonX, rather we are using Lepton. Is there any attempt to correct this for the Lepton theme as well? I notice the above conversation only referring to the LeptonX theme.
Also, is there a temporary workaround for the Lepton theme?
As another ABP customers reported, this wasn't an issue in previous versions of ABP Blazor Server.
Hi @liangshiwei,
We deployed a newly templated ABP app to an Azure Azure Appservice that only includes our Sendgrid implementation for sending emails and everything worked as expected.
After further research - under certain conditions, it appears that the Azure platform is performing scanning/prefetching of the password reset link in the email, causing the ABP exceptions.
We updated the SPF and DKIM settings for our sending domain and upgraded our Sendgrid account from a free plan to a paid plan.
After performing these actions everything seems to be working fine.
My thinking is that the free Sendgrid plan included something in the email headers that was triggering Azure to scan the emails and prefetch the email's link.
Hope this information helps someone else.
I will try that and let you know what we find...
Hi,
Yes, this is strange.
We looked at logging and we can see that the http request for Account/ForgotPassword and Account/PasswordResetLinkSet is originating from the client, but the problem/unusual http request for Account/ResetPassword is originating from IP addresses in Microsoft's Data Centers (Azure platform running the ABP application).
Hi,
We do have multiple environments. We handle this with appsettings.json as follows: