Activities of "improwise"

[maliming] said: hi

I think there will be no exception if you run the api by dotnet run command.

If so, you can ignore this exception in VS.

Thanks.

I believe this is something that should be handled better in the code, as this would require manual configuration in every project using the Chat module which should not be needed.

Thanks.

[maliming] said: hi

We will adjust Angular to display name and surname in the next patch version.

Also, how could we disable/hide everything but the logout button in this absurdly complicated user menu that make it seem like you are logged in as an admin even though it is a normal user?

Our Angular team will guide you in removing the menu items.

For MVC:

You can add a new MyUserMenuContributor to remove them.

PostConfigure<AbpNavigationOptions>(options => 
{ 
    options.MenuContributors.Add(new MyUserMenuContributor()); 
}); 
public class MyUserMenuContributor : IMenuContributor 
{ 
    public virtual Task ConfigureMenuAsync(MenuConfigurationContext context) 
    { 
        if (context.Menu.Name != StandardMenus.User) 
        { 
            return Task.CompletedTask; 
        } 
 
        context.Menu.TryRemoveMenuItem("Account.LinkedAccounts"); 
        context.Menu.TryRemoveMenuItem("Account.AuthorityDelegation"); 
        context.Menu.TryRemoveMenuItem("Account.ExternalLogins"); 
 
        return Task.CompletedTask; 
    } 
} 
 

Thanks.

Thanks you.

Please consider refunding this ticket as it seems it identified a problem.

Also, how could we disable/hide everything but the logout button in this absurdly complicated user menu that make it seem like you are logged in as an admin even though it is a normal user?

At least with the Angular UI, if you install and enable the Chat module, it will throw exceptions at every page load

This goes away if you disable chat module so the source of the error is quite obvious.

Not sure what real user impact this has but at least it makes debugging much more complex as you will constantly have it break here (or have to put in rules for ignoring exceptions)

Thanks.

This seem to be related

https://abp.io/support/questions/5889/Use-user-first-name-and-last-name-on-the-menu-profile--instead-of-user-name-in-ABPUSer-table

but seems complicated and will probably break if LeptonX theme is updated.

We would ideally just want to his the username below the profile picture, and then have all UIs show Firstname Lastname when you go into the user accont menu (like with the MVC UI)

Ai instructions seems wrong here, referring to non existent files etc

Hi,

It seems like ABP breaks when you are using longer usernames like "reallylongusername"

there also seems to be inconsistencies between UIs, above is angular UI, below is the same page in My Account for API (which I think is MVC)

One displays name, the other one displays username.

<br> Why is different UIs showing different things (username vs firstname and lastname) for same page?

How can we modify/change this so that a truncated username is not shown and also which properties are shown (username, firstname, lastname etc)

Thanks.

Please fix the servicebot closing unresolved issues

ABP support team answer please

We are looking to integrate an external OIDC identity provider as a social/external login in our ABP Commercial application, following the Account Pro module documentation (AddOpenIdConnect + WithDynamicOptions). The OIDC provider we need to integrate only supports private_key_jwt as the token endpoint authentication method — meaning no client_secret_basic or client_secret_post is available. The current documented pattern assumes a client secret, which doesn't apply when using private_key_jwt (where the client authenticates by signing a JWT with a private key instead).

Some questions:

1. Does ABP Commercial have any existing support or documented approach for external OIDC providers that require private_key_jwt authentication?

2. Is there any planned support for private_key_jwt in the external login infrastructure — for example as part of WithDynamicOptions or the Account Pro module?

3. If we implement this ourselves via OpenIdConnectEvents customization, are there any ABP-specific pitfalls we should be aware of — particularly around how this interacts with OpenIddict, the Account module's external login flow, and user creation/mapping?

https://oauth.net/private-key-jwt/

Any guidance or pointers would be appreciated.

Thanks