Activities of "lba"

We're having a problem with antiforgery when trying to verify a users email (under "/Account/Manage" -> Personal info).

The value of XSRF-TOKEN is added to request headers as value for RequestVerificationToken

But the application responds with an error and logs a warning "The antiforgery cookie token and request token do not match".

Upon retrying to request email verification, everything works as expected.

Previously, we configured AbpAntiForgeryOptions as follows:

Configure<AbpAntiForgeryOptions>(options =>
{
    options.TokenCookie.SameSite = Microsoft.AspNetCore.Http.SameSiteMode.None;
    options.TokenCookie.SecurePolicy = Microsoft.AspNetCore.Http.CookieSecurePolicy.Always;
});

Without the above code, RequestVerificationToken would not get added to request headers and email verification did not work at all.

Interestingly, the problem exists only in production environment. No errors occur in development environment.

We look forward to any input on this matter.

  • ABP Framework version: v8.2.2
  • UI Type: Blazor Server
  • Database System: EF Core
  • Steps to reproduce the issue:
    • Using Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton, insert MenuItem into navigation bar.
    • Navigate to the page the item points to by other means (like HTML anchor element).

When using the navigation bar to navigate, the corresponding MenuItem is set as "current".

We use custom CSS to indicate to the user which part of the application they're currently at (green underline, as seen in the images above). The user may also be redirected to a different part of the application when interacting with elements outside of the navigation bar. In that case, the corresponding MenuItem is not set as "current" (as shown in the image below).

How can this behaviour of setting a MenuItem as "current" be replicated when using other means (like HTML anchor element) to navigate to the same page?

  • ABP Framework version: v7.2.2
  • UI Type: Blazor Server
  • Database System: EF Core
  • Steps to reproduce the issue:
    • Using Volo.LanguageManagement, change value for the key of a text
    • Login with tenant

When using Volo.LanguageManagement to update texts, the changes are not reflected when switching between tenants.

Example We want to change the text from "New Project" in the header to "hello"

Upon saving, the text was changed without any issues.

However, when logging in with a tenant, the header still displays "New Project", as the value appears unchanged in the language management module.

How can we use the language management module for tenant-independent localization?

Showing 1 to 3 of 3 entries
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.1.0-preview. Updated on November 17, 2025, 08:31
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.