Activities of "Rishi1532"

Hi,

Thank you for the information.

We’ve collected the debug logs for issue #9502 – "Cypress POST Requests Returning 400 Bad Request – Works Fine in Browser" and have sent them directly via email to liming.ma@volosoft.com.

Please confirm once received. Let us know if any additional details are needed.

Thanks

Hi,

Thank you for the response.

We’ve enabled debug logging as per the instructions provided in this guide.

Could you please let us know the preferred way to share the debug log files with you for the 400 error issue we’re encountering?

Looking forward to your guidance.

Best regards, Rishikesh Tuniki

hi we have used the recommendations from the answer you have provided added this in the HttpApiHostModule > configureServices method Configure<AbpAntiForgeryOptions>(options => { options.TokenCookie.Domain = ".aumtech.org"; // Use your actual parent domain options.TokenCookie.SecurePolicy = CookieSecurePolicy.None; options.TokenCookie.SameSite = SameSiteMode.Lax; // or SameSiteMode.None if using HTTPS });

we still received the same error

and 4th point id not applicable as we are using data center Linux server for hosting

[maliming] said: hi

The latest 8.x version is 8.3.4

https://www.nuget.org/packages/Volo.Abp.EntityFrameworkCore/8.3.4

Your code seems to have no problem. You can run it. Feel free to provide feedback on any exceptions/problems.

Thanks.

hi, Thanks this solved my issue

Hi

Additionally, I’ve updated the DbContextFactory and EntityFrameworkCoreModule files to use .UseNTi(...) as per the Aumerial provider's documentation. Could you kindly confirm if these changes will work as expected, or if there’s anything else I need to adjust for full compatibility?

DbContextFactory

using System.IO; using Microsoft.EntityFrameworkCore; using Microsoft.EntityFrameworkCore.Design; using Microsoft.Extensions.Configuration; using Aumerial.EntityFrameworkCore; // Check Aumerial's NuGet package

namespace NTIDemo.EntityFrameworkCore;

public class NTIDemoDbContextFactory : IDesignTimeDbContextFactory<NTIDemoDbContext> { public NTIDemoDbContext CreateDbContext(string[] args) { var configuration = BuildConfiguration();

    NTIDemoEfCoreEntityExtensionMappings.Configure();

    var builder = new DbContextOptionsBuilder<NTIDemoDbContext>()
        .UseNTi(configuration.GetConnectionString("Default")); // Replace with Aumerial's method

    return new NTIDemoDbContext(builder.Options);
}

private static IConfigurationRoot BuildConfiguration()
{
    var builder = new ConfigurationBuilder()
        .SetBasePath(Path.Combine(Directory.GetCurrentDirectory(), "../NTIDemo.DbMigrator/"))
        .AddJsonFile("appsettings.json", optional: false);

    return builder.Build();
}

}

EntityFrameworkCoreModule

using System; using Microsoft.Extensions.DependencyInjection; using Volo.Abp.Uow; using Volo.Abp.AuditLogging.EntityFrameworkCore; using Volo.Abp.BackgroundJobs.EntityFrameworkCore; using Volo.Abp.EntityFrameworkCore; using Volo.Abp.FeatureManagement.EntityFrameworkCore; using Volo.Abp.Identity.EntityFrameworkCore; using Volo.Abp.OpenIddict.EntityFrameworkCore; using Volo.Abp.Modularity; using Volo.Abp.PermissionManagement.EntityFrameworkCore; using Volo.Abp.SettingManagement.EntityFrameworkCore; using Volo.Abp.BlobStoring.Database.EntityFrameworkCore; using Volo.Abp.LanguageManagement.EntityFrameworkCore; using Volo.FileManagement.EntityFrameworkCore; using Volo.Abp.TextTemplateManagement.EntityFrameworkCore; using Volo.Saas.EntityFrameworkCore; using Volo.Abp.Gdpr; using Volo.Chat.EntityFrameworkCore; using Volo.Abp.Studio; using Aumerial.EntityFrameworkCore; using Microsoft.Extensions.Configuration;

namespace NTIDemo.EntityFrameworkCore;

[DependsOn( typeof(NTIDemoDomainModule), typeof(AbpPermissionManagementEntityFrameworkCoreModule), typeof(AbpSettingManagementEntityFrameworkCoreModule), typeof(AbpBackgroundJobsEntityFrameworkCoreModule), typeof(AbpAuditLoggingEntityFrameworkCoreModule), typeof(AbpFeatureManagementEntityFrameworkCoreModule), typeof(AbpIdentityProEntityFrameworkCoreModule), typeof(AbpOpenIddictProEntityFrameworkCoreModule), typeof(LanguageManagementEntityFrameworkCoreModule), typeof(FileManagementEntityFrameworkCoreModule), typeof(SaasEntityFrameworkCoreModule), typeof(ChatEntityFrameworkCoreModule), typeof(TextTemplateManagementEntityFrameworkCoreModule), typeof(AbpGdprEntityFrameworkCoreModule), typeof(BlobStoringDatabaseEntityFrameworkCoreModule) )] public class NTIDemoEntityFrameworkCoreModule : AbpModule { public override void PreConfigureServices(ServiceConfigurationContext context) { // https://www.npgsql.org/efcore/release-notes/6.0.html#opting-out-of-the-new-timestamp-mapping-logic

    NTIDemoEfCoreEntityExtensionMappings.Configure();
}

public override void ConfigureServices(ServiceConfigurationContext context)
{
    context.Services.AddAbpDbContext<NTIDemoDbContext>(options =>
    {
            /* Remove "includeAllEntities: true" to create
             * default repositories only for aggregate roots */
        options.AddDefaultRepositories(includeAllEntities: true);
    });

    if (AbpStudioAnalyzeHelper.IsInAnalyzeMode)
    {
        return;
    }

    Configure<AbpDbContextOptions>(options =>
    {
        options.Configure<NTIDemoDbContext>(context =>
        {
            var configuration = context.ServiceProvider.GetRequiredService<IConfiguration>();
            context.DbContextOptions.UseNTi(configuration.GetConnectionString("Default"));
        });
    });



}

}

Looking forward to your guidance.

Best regards, Rishikesh

Hi Thank you for the helpful responses.

Since the Aumerial.EntityFrameworkCore provider is compatible with EF Core 8, I understand that I’ll need to downgrade my ABP solution to an earlier version that also uses EF Core 8.

Could you please confirm which ABP Framework version (e.g., 8.x.x) would be the most stable and compatible for working with EF Core 8 and the Aumerial provider for IBM i (Db2)?

I’d like to ensure I’m using a version that maintains long-term support and minimal compatibility issues with the rest of the ABP ecosystem.

Thanks again for your support!