Activities of "gterdem"

Check your administrationService authserver configuration. It seems is it configured as https://auth-server-v1.mycustomdomain. So when you make a request, it tries to validate at this endpoint. However, it should check http://auth-server-v1.mycustomdomain in the internal network.

Did you add http://medistat.co.za? Does it solve the problem?

If is it about your local k8s cluster, you need to create self-signed certificate for your local machine. If it is about the production environment, you can use lets-encrypt as a cluster-issuer.

The Angular application is the back-office (admin) application for your microservice solution while the MVC application is the landing-page (public) application. See more on Microservice startup template docs.

You can either develop UI as a monolith or modular. See more on UI development docs. For example, ProductService is a sample for modular UI development for MVC, hosting Web layer inside the microservice. Currently, we do not support modular development for angular. You need to use some libraries like angular module federation or other micro-frontend libraries.

"CorsOrigins": "https://*.Medistat.com,https://medistat.co.za/MedistatWeb,http://medistat.co.za/MedistatWeb,https://localhost:4200",

You allow https://medistat.co.za but you are making request from http.

When you are using the non-separate Angular template, IdentityServer library is embedded to Http.Api.Host project (backend) instead of a different runnable project.

You can create a new non-separate Angular template and move your business code to the new project. Or you can examine and compare the non-separate template with your current template and move the IdentityServer to Http.Api.Host.

If your application doesn't require to be modular, you can also try the single-layer template with angular UI.

This is the same issue as reported here (applies to 5.2.2 and 5.3.0-RC1): https://support.abp.io/QA/Questions/3067/530-RC1-Form-Multi-tenant-issue

Yes, they seem same issue.

Thank you, we'll investigate more based on the steps in https://support.abp.io/QA/Questions/3067/530-RC1-Form-Multi-tenant-issue

Add

Microsoft.IdentityModel.Logging.IdentityModelEventSource.ShowPII = true;

to related application/microservice modules to see the detailed error.

Sorry, I am not available for remote sessions. But these are the steps I have followed:

I had removed ABP CLI to install ABP CLI version 4.4.3 in order to create a Blazor application for version 4.4.3.

Updated the Index.razor.cs file:

namespace MyApp.Blazor.Pages
{
    [Authorize]
    public partial class Index
    {

    }
}

This configuration automatically redirects the application to login page. Update MyAppBlazorModule.cs file:

private static void ConfigureAuthentication(WebAssemblyHostBuilder builder)
{
    builder.Services.AddOidcAuthentication(options =>
    {
        builder.Configuration.Bind("AuthServer", options.ProviderOptions);
        options.UserOptions.RoleClaim = JwtClaimTypes.Role;
        options.AuthenticationPaths.LogOutSucceededPath = "/";
        options.ProviderOptions.DefaultScopes.Add("MyApp");
        options.ProviderOptions.DefaultScopes.Add("role");
        options.ProviderOptions.DefaultScopes.Add("email");
        options.ProviderOptions.DefaultScopes.Add("phone");
    });
}

Result:

Can you add more details about your problem like some screenshots that explain the problem?