Activities of "shodgson"

Hey, thanks for the response.

Unless i'm mistaken, the auth server requests targeting the /api/account/my-profile within the Account/Manage page does not go through the web gateway.

Locally, when running everything as default and without any custom base path for my auth server, I do see all /api/account/my-profile requests reaching the auth server directly without going through the web gateway. I can repro the same behavior when starting from a new microservice template.

Repro steps:

• Create a new microservice solution with a Blazor web app
• Go on the /Account/Manage page hosted on the auth server
• Change password and submit
• Notice that the /api/account requests are directly sent to the auth server and not the web gateway

Hello,

We're using the ABP microservice template for a blazor web app that is deployed on AKS.

Our auth server is currently deployed and reachable on a /auth path.

When trying to Submit the personal info or change password on the "My account" page of the auth server we get a 404. In the network tab we see that our /auth base path is not in the url used to do the request even though we have properly set the app.UsePathBase("/auth") in the auth server module.

Is there anything other than the base path that needs to be set in order to get the auth/account actions working under a base path on the auth server?

Thanks

Hi,

Thanks to the information you provided, I was able to reproduce the problem. The problem does not occur in the Application Layered template, but in the Microservice solution, so I could not reproduce it the first time. I will create an internal issue, and we will keep you informed about the progress. Thank you for your patience.

Thank you,

I'll wait for an issue link to track the progress

Thanks for the response.

Unfortunately it seems I can reproduce the issue even on a new microservice solution.

I'm on version 9.1

Steps to reproduce on my side:

• Create a new microservice solution from the abp studio
• EF Core database provider
• Multitenancy enabled
• Blazor WebApp as the UI framework
• No mobile framework
• No public website
• No dynamic localization
• OpenIddict UI enabled
• LeptonX theme
• Add this block in the .Client assembly in the MenuContributor file

 var currentTenant = context.ServiceProvider.GetRequiredService<ICurrentTenant>();

 Console.WriteLine($"Running on the browser: {OperatingSystem.IsBrowser()} Current tenant is {currentTenant.Id}: {currentTenant.Name}");

• Run the solution and create a tenant
• Login on that new tenant and notice the empty tenantid/tenantname in the console
• 

Hello,

i'm currently trying to get the CurrentTenant information within the context of a custom IMenuContributor. When the ConfigureMenuAsync executes on the server side the current tenant id is properly populated from the ICurrentTenant implementation but it is null when executing for web assembly. Here's my ConfigureMainMenuAsync from a custom IMenuContributor which is properly registered on the menu contributors

    private static async Task ConfigureMainMenuAsync(MenuConfigurationContext context)
    {
        var l = context.GetLocalizer<MyResource>();

        var currentTenant = context.ServiceProvider.GetRequiredService<<ICurrentTenant>ICurrentTenant>();        

        // Prints the current tenant id/name on the server
        // Prints null on web assembly
        Console.WriteLine($"Current tenant is {currentTenant.Id}: {currentTenant.Name}");

        if (currentTenant.Id == null)
        {
            // Custom logic for the Host
        }
    }

Any ideas why that is?

Thanks !!