Activities of "maliming"

hi

Are these cookies in the same domain and port?

Yes.

hi

You can set the log level in code.

hi

No need for EnableSensitiveDataLogging

You can share current logs.

Thanks.

hi

Can you share full logs.txt?

See https://abp.io/support/questions/8622/How-to-enable-Debug-logs-for-troubleshoot-problems

Hi

Can you check if the request contains the authentication cookies in Chrome devtool?

You’re not using tiered blazor project. Right?

Settings file 'DotnetToolSettings.xml' was not found in the package

You can install the latest official NET 9 SDK to solve this issue.

https://dotnet.microsoft.com/en-us/download/dotnet/9.0

hi

The web app has two modes, server and wasm.

CookieBased means you don't need to get the access token because of the authentication state in the cookies.

You can request the API, The browser will add the cookies automatically.

hi junio

Enable debug logs and reproduce the problem, then share the logs.txt file with liming.ma@volosoft.com

https://abp.io/support/questions/8622/How-to-enable-Debug-logs-for-troubleshoot-problems

Thanks.

When you encounter problems in the development or production environment, we would like to see the log to troubleshoot the problem.

.MinimumLevel.Debug() will set MinimumLevel to Debug to show more logs.

We don't want to see EF Core's Debug logs when your problem has nothing to do with EF Core.

var loggerConfiguration = new LoggerConfiguration()
    .MinimumLevel.Debug()
    .MinimumLevel.Override("Microsoft.EntityFrameworkCore", LogEventLevel.Warning)
    .Enrich.FromLogContext()
    .WriteTo.Async(c => c.File("Logs/logs.txt"))

If you have an EF Core-related problem, you can remove MinimumLevel.Override("Microsoft.EntityFrameworkCore", LogEventLevel.Warning) and EnableSensitiveDataLogging to see EF Core debug logs.

Configure<AbpDbContextOptions>(options =>
{
    /* The main point to change your DBMS.
     * See also BookStoreMigrationsDbContextFactory for EF Core tooling. */
    Configure<AbpDbContextOptions>(options =>
    {
        options.Configure(actions =>
        {
            actions.UseSqlServer();
            actions.DbContextOptions.EnableSensitiveDataLogging();
        });
    });
});

If your API website experiences a JWT authentication problem, please ShowPII and output identity model logs.

 public async static Task<int> Main(string[] args)
{
    IdentityModelEventSource.ShowPII = true;

    IdentityModelEventSource.Logger.LogLevel = EventLevel.Verbose;
    var wilsonTextLogger = new TextWriterEventListener("Logs/identitymodel.txt");
    wilsonTextLogger.EnableEvents(IdentityModelEventSource.Logger, EventLevel.Verbose);

See: https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/wiki/PII https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/wiki/How-to-log-from-IdentityModelEventSource.Logger

If you have an OpenIddict related problem, please override the OpenIddict log level to Verbose.

var loggerConfiguration = new LoggerConfiguration()
    .MinimumLevel.Debug()
    .MinimumLevel.Override("Microsoft.EntityFrameworkCore", LogEventLevel.Warning)
    .MinimumLevel.Override("OpenIddict", LogEventLevel.Verbose)
    .Enrich.FromLogContext()
    .WriteTo.Async(c => c.File("Logs/logs.txt"))