Activities of "DominaTang"

Hi, For the project that I am upgrading from Ocelot (with ABP 8) to Yarp (ABP 10) The gateway module has this code:

app.UseSwagger();
        app.UseSwaggerUI(options =>
        {
            ...
        });
        app.UseAbpSerilogEnrichers();
        **app.MapWhen(
            ctx => ctx.Request.Path.ToString().StartsWith("/api/abp/api-definition") ||
                   ctx.Request.Path.ToString().TrimEnd('/').Equals(""),
            app2 =>
            {
                app2.UseRouting();
                app2.UseConfiguredEndpoints();
            }
        );**

        //For signalR
        app.UseWebSockets();
        app.UseOcelot().Wait();
        

new code: app.UseSwagger(); app.UseAbpSwaggerUI(options => { ConfigureSwaggerUI(proxyConfig, options, configuration); }); app.UseAbpSerilogEnrichers(); app.UseRewriter(CreateSwaggerRewriteOptions()); app.UseWebSockets(); app.UseEndpoints(endpoints => endpoints.MapReverseProxy());

Did I miss anything about the app.MapWhen in new code?

When migrate from Ocelet to yarp, by default, an separate yarp.json file is added. When I use yarp file and code has .AddYarp() statement, I noticed that public gateway micro service swagger would only expose those APIs I defined in yarp, however, because of our existing CI/CD, I put yarp.json content to appsettings.json, I noticed that gateway swagger can see all APIs from all micro-service.

Did I miss anything?

The top-level package is Volo.Abp.Http.Client.IdentityModel 10.1.1, which pulls in Volo.Abp.IdentityModel, which in turn depends on Microsoft.IdentityModel.* 6.26.1 and System.IdentityModel.Tokens.Jwt 6.26.1.

Can ABP package upgrade to System.IdentityModel.Tokens.Jwt version 8?

Just wondering except for: Configure<AbpClockOptions>(options => { options.Kind = DateTimeKind.Utc; // recommended in ABP });

Is it possible set the IClock to certain time zone, eg EST, so when using Clock.Now, it is EST's time?

When upgrade from ABP8 to ABP 10, follow Mapperly migration guide web page, the old code just simply sentence to map from IdentityUser to IdentityUserEto, with new code:

We are going to upgrading ABP 8 to ABP 10 (Micro Services template) I noticed that since ABP9, each MicroService project layout is simplified,

Now it becomes

But I feel like for a system already go lives for years, It is safer to continue using legacy ABP Cli doing the upgrade so that the projects layout would not change significantly.

ABP would keep upgrading legacy ABP cli, right? Any suggestion?

I forgot which is the first version of ABP that replace Ocelot to Yarp, do you know about it?

I noticed that ABP 9 introduced "Entity Cache", if a an Entity has navigation properties, for example, a Product has a list of Orders. If I register Product for entity cache, when Order is changed or added to the product, would the cached product has latest orders list?

When an tenant has 2FA enabled, it's not able for automation API testing. So when a tenant has 2FA enabled, could particular user account has it disabled? If yes, which database table shall I check the value? Is there admin UI for it?

Or do you have any other better idea for backend API automation testing?

Hi,

We noticed that when the application (Micro Service template) is deployed to Azure Kubernetes, Applications insight show the application throw 401 exception, the error details as below:

Failed to refresh remote claims for user: ae264b2c-aa17-336e-500c-3a0f39672a03 Volo.Abp.AspNetCore.Authentication.JwtBearer.DynamicClaims.WebRemoteDynamicClaimsPrincipalContributorCache

Do you have any clue about the error?

Thanks,