"tony.chen@sjrb.ca" 'in aktiviteleri

Do we have any documentation on using LeptonX components? One example: https://x.leptontheme.com/side-menu/libraries/datatables

I know under the hood it's using this lib: https://datatables.net/ , but I still need know how LeptonX bootstrap this by using <abp-?> tag or some other examples.

also, where is the source code on this LeptonX Pro and demo site? I downloaded this source code: Volo.Abp.LeptonXTheme.Pro but don't see anything on how to use components.

• ABP Framework version: v8.1.2
• UI Type: MVC
• Database System: EF Core (PostgreSQL)
• Tiered (for MVC): yes
• Exception message and full stack trace: 404 on loading css and js
• Steps to reproduce the issue: put round robin on routing and deploy 2+ mvc web service instances

The issue is lazy bundling on script and css. Each instance has it's own unique hash key. (ex: /__bundles/LeptonX.Global.8923ECD9CC3A022B71E966D19950185C.js?_v=638515137047135053). When we have multiple instances with round robin setup in loading balance, users get 404 response on loading script and css source files.

Is there any way to pre-generate the source file during build stage? so application doesn't do bundling on the fly and avoid inconsistent hash keys across all instances?

• ABP Framework version: v7.0.2
• UI type: Angular
• DB provider: EF Core
• Identity Server Separated (Angular): yes
• Exception message and stack trace: Get this error when click logout button in angular site error:invalid_token error_description:The signing key associated to the specified token was not found. error_uri:https://documentation.openiddict.com/errors/ID2090
• Steps to reproduce the issue:" login then logout(/connect/logout?id_token_hint=...)

We are getting invalid_token error after click logout button from Angular site when openiddict auth service running in load balance mode. (no issue if we only run one auth instance) Is there any specific setting has to be done for supporting Angular? The MVC site running inside of auth service doesn't have this issue.(maybe because of using cookie)

//we are using a shared symmetrickey and protection-key from redis

PreConfigure<OpenIddictServerBuilder>(builder =>
{
   builder.AddSigningKey(new SymmetricSecurityKey(...));
});