Hi,
We have an tiered modular application, abp version 9.2.0, database postgresql. Not sure if it is related but mentioning, we migrated from mysql previously and upgrade from abp 8.3.0. We’re investigating a timezone/filtering problem with ABP audit/security logs and would like to confirm the correct approach.
Audit log and security log date filters behave differently between local and cloud hosted environments. The __timezone header is present on requests, but filtering still appears incorrect and does not return the results relevant to the timezone, even with the ClockOptions.Kind set to DateTimeKind.Utc and the app.UseAbpTimeZone() middleware. We also have EnableLegacyTimestampBehavior set to true in the DbContext, but i suspect that this part of the problem as the EF module snapshots still define the timestamp columns as timestamps with time zone.
Supporting information: Incoming request log (from our host probe): Audit timezone probe Path=/api/audit-logging/audit-logs __timezone=Africa/Johannesburg startTime=2026-07-02T14:02:00.000 endTime= DB sample audit rows are stored as UTC/timestamptz, e.g. 2026-07-02 11:40:59.564458+00. Code pointers in our repo (current state): AppContext.SetSwitch("Npgsql.EnableLegacyTimestampBehavior", true) exists in: EntityFrameworkCoreModule.cs Migrations/snapshots show columns created as timestamp with time zone across modules (e.g. src/EntityFrameworkCore/Migrations/* and module snapshots).
modelBuilder.Entity("Volo.Abp.Identity.IdentitySecurityLog", b =>
{
b.Property<Guid>("Id")
.ValueGeneratedOnAdd()
.HasColumnType("uuid");
b.Property<DateTime>("CreationTime")
.HasColumnType("timestamp with time zone");
});
Is my understanding correct that with Npgsql.EnableLegacyTimestampBehavior = true the runtime may interpret ambiguous/unspecified DateTime values using host-local timezone, causing behavior differences between local and UTC-hosted environments? Is that the intended/known effect of the legacy switch?
If we set Npgsql.EnableLegacyTimestampBehavior to false (or remove the AppContext.SetSwitch), will that cause incompatibility with existing data or require database migrations or data fixes? Any known upgrade pitfalls? Why is model snapshot still defining the timestamp related columns as timestamp with time zone if I have set Npgsql.EnableLegacyTimestampBehavior = true?
For an ABP v10 project, what is the recommended setting for Npgsql.EnableLegacyTimestampBehavior when using timestamp with time zone (timestamptz) for audit/security timestamps? Why do some ABP templates/solutions still set the switch to true by default — is that for backward compatibility? Are there official migration steps documented by ABP when switching off legacy behavior?
Do you recommend (a) keeping timestamptz and disabling legacy behavior or (b) switching to timestamp without time zone and handling conversion application-side? Template: app Version 9.2.0
Tiered: Yes
UI Framework: angular
Theme: leptonx
Theme Style: system
Progressive Web App: Yes
Database Provider: ef
Database Management System: postgresql
Separate Tenant Schema: Yes
Mobile Framework: none
Public Website: No
Optional Modules:
LanguageManagement
AuditLogging
SaaS
OpenIddictAdmin
Hi,
We have need to define multiple different ABP based solutions and yet still use the same openiddict auth server for a single sign on experience and central management of users, roles and permissions. The auth server has been configured and the client applications including the other client api's (ie. the host api's of the various modules) have been registered. The redirect works and a valid token is issued, however the authentication and authorization fails in the host api. We are able to get this working, if we manually create the tenant, the user and the session record in the database that is used by the host api. Can we programmatically create the tenant if it doesn't exist, create the user if it doesn't exist, and the session context for that user so that ICurrentUser and ICurrentTenant works? Alternatively is there a different approach we can take to take to implement this?
ABP Version - 9.2.0
Hi,
Can you provide us a with a single migration that needs to be applied for both the host and tenant when upgrading from 8.3.0 to 9.2.0? Here is the solution configuration:
Hi,
Is there a problem with nuget.abp.io? Recently our Azure DevOps builds are failing when attempting to install the cli and/or when attempting to install nuget packages,
Here is the script to install the CLI: dotnet tool install -g Volo.Abp.Studio.Cli It fails with the following error: Response status code does not indicate success: 403 (Forbidden).
Similarly, when attempting to install nuget packages: Determining projects to restore... Retrying 'FindPackagesByIdAsync' for source 'https://nuget.abp.io/ {{redacted}} /v3/package/volo.abp.users.abstractions/index.json'. Response status code does not indicate success: 403 (Forbidden).
Regards, Lucian
Hi,
How can I update/customize the login page of the account pro module (note: separated openiddict auth server) so that we can personalize it for our use case? As an example, changing the background image or updating the text on the buttons etc. I would assume that we would either need the code for login view and override it entirely or there is a way to update parts of it?
