Activities of "balessi75"

Excellent, thanks!

Thanks @maliming. Will this make the 7.3 release?

Hi,

The UI is Blazor Server using the Lepton theme.

Thanks

ABP Commercial 7.2.1 / Blazor Server / EF / Non tiered / Separate Host and Tenant DBs / Lepton Theme

Hi,

In 7.2.1, when a tree view node drop down item is clicked, previously opened drop down menu's don't close causing some confusion to the user. Depending on the overlaying of drop down menus, the user can get in a situation where a drop down menu can't be collapsed on their own.

Is there any way to have a previously opened dropdown menu be programmatically closed when a new one is opened?

Thanks in advance.

Brian

For anyone running into this problem, I upgraded MacOS to the latest version which also updated Safari and the issue was resolved.

ABP Commercial 7.2.1 / Blazor Server / EF / Non tiered / Separate Host and Tenant DBs / Lepton Theme

Hi, we are receiving the following exception in certain circumstances when a user logs in (see below for full log details)

The antiforgery cookie token and request token do not match.

So far, we only seem to have been able to replicate this in a Safari browser running on a Mac. We have not been able to replicate the issue on Chrome or Edge whether on a PC or Mac.

Steps to reproduce:

1. Start with a clean slate by clearing the browser cache
2. Login as a user
3. Logout
4. Login as the same user
5. Logout
6. On the third login as the same user, the user receives a HTTP 400 AN INTERNAL ERROR OCCURRED DURING YOUR REQUEST! message.
7. From that point the user cannot login again without an exception (even if using a new tab or restarting the web browser). Additionally any invalid credentials entered causes the exception instead of the user friendly 'Invalid username or password' message.
8. The only way for the user to login again at this point is to clear the browser cache

The above steps are very repeatable, but it is a strange sequence of events. This is the only way we can reproduce, but a few clients have reported the issue as occurring randomly.

We are using HTTPS only have not found anything in our research that seems to apply to our situation.

Any suggestions on what might be going on here and if there are any known issues and/or workarounds?

Logging Details:

2023-05-26 02:23:20.497 +00:00 [INF] Executing endpoint '/Account/Login'
2023-05-26 02:23:20.497 +00:00 [INF] Route matched with {page = "/Account/Login", area = "", action = "", controller = ""}. Executing page /Account/Login
2023-05-26 02:23:20.497 +00:00 [INF] Skipping the execution of current filter as its not the most effective filter implementing the policy Microsoft.AspNetCore.Mvc.ViewFeatures.IAntiforgeryPolicy
2023-05-26 02:23:20.498 +00:00 [INF] Antiforgery token validation failed. The antiforgery cookie token and request token do not match.
Microsoft.AspNetCore.Antiforgery.AntiforgeryValidationException: The antiforgery cookie token and request token do not match.
   at Microsoft.AspNetCore.Antiforgery.DefaultAntiforgery.ValidateTokens(HttpContext httpContext, AntiforgeryTokenSet antiforgeryTokenSet)
   at Microsoft.AspNetCore.Antiforgery.DefaultAntiforgery.ValidateRequestAsync(HttpContext httpContext)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.Filters.ValidateAntiforgeryTokenAuthorizationFilter.OnAuthorizationAsync(AuthorizationFilterContext context)
2023-05-26 02:23:20.498 +00:00 [INF] Authorization failed for the request at filter 'Microsoft.AspNetCore.Mvc.ViewFeatures.Filters.AutoValidateAntiforgeryTokenAuthorizationFilter'.
2023-05-26 02:23:20.498 +00:00 [INF] Executing StatusCodeResult, setting HTTP status code 400

Ok, so this start happening after the ABP upgrade to 7.2.1, does that mean that ABP 7.2.1 is using a later version of Blazorise which is causing the issue?

Do you know if Blazorise is aware of the issue and if they will be working on it?

Thanks

ABP Commercial 7.2.1 / Blazor Server / EF / Non tiered / Separate Host and Tenant DBs / Lepton Theme

We are currently deploying our ABP solution to an Azure App Service using an Azure DevOps build pipeline that fires off an automated build and release based on commits to an environment specific code branch (dev, qa, staging, etc).

To date, we've been manually running the ABP DbMigrator project from VS against our environment specific Azure SQL DB (dev, qa, staging, etc) whenever new migrations exists. The DbMigrator.exe is great in that it automatically applies schema changes to each tenant separated DB that is defined in the host database.

We would like the DbMigrator process to be automated and synched with the web application deployment using our existing CI/CD process and it's not clear how to set this up.

I'm guessing the DBMigrator.exe would have to be built and deployed somewhere that has access to the host DB running in Azure so that it could be run against it.

Does anyone have any guidance or suggestions on the best approach to accomplish this type of scenario?

Thanks in advance,

Brian

FYI, this appears to be happening on all ABP CRUD management areas, not just User Management. I just noticed it in Tenant Management.

Thanks @maliming