Activities of "maliming"

hi

You can try:

using (CurrentPrincipalAccessor.Change(new Claim(AbpClaimTypes.UserId, userid)))
{
    //...
}

hi

1.

You can check it using browser dev tools to see what's happening.

2.

Please check your application logs. You can share it here.

3.

Does it work locally without docker? dotnet run Do you have steps to reproduce it?

hi

Please share full error/exception logs. Thanks

hi

You can add userid to the background job parameters.

hi

I don't have it You can google it.

https://www.google.com/search?newwindow=1&q=asp+net+core+WSo2+API

There are a lot of documentations.

hi

We use standard authentication and authorization of asp net core.

https://docs.abp.io/en/abp/latest/Authorization https://docs.abp.io/en/abp/latest/Authorization#advanced-topics

On the Angular side, I suppose we need to create our own guards and check the configuration to evaluate the permissions, or something along those lines.

I think so.

hi

I think you can override the (ChatIconComponent)chat-icon.component.ts

https://docs.abp.io/en/abp/latest/UI/Angular/Component-Replacement

hi

We use oauth2 and standard asp net core authentication and authorization in microservices, you only need to integrate according to the documentation of wso2 API.

hi

Maybe the cookies are different in local and production.

https://docs.abp.io/en/abp/latest/Multi-Tenancy#default-tenant-resolvers

hi

You can add your code to:

app.Use(async (ctx, next) =>
{
    if (ctx.User.Identity?.IsAuthenticated != true)
    {
        var result = await ctx.AuthenticateAsync("jwt2");
        if (result.Succeeded && result.Principal != null)
        {
            // add your logic
            ctx.User = result.Principal;
            // add your logic

        }
    }

    await next();
});