Activities of "nhontran"

• ABP Framework version: v5.2.2
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:"

Hi, we are having issue when upgrade our project from ABP 3.3.2 to 5.2.2, it does not work on IE browser, I know IE browser has ended support but one group of our users still require it for now.

Could you please advise us how to fix this issue?

• ABP Framework version: v5.2.2.
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:"

Hi, we have upgraded our solution to Abp 5.2.2 and got 1 issue when accessing the TenantSwitchModal, we are not allowed to add 'unsafe-eval' into script-src due to security test, below is our CSP:

default-src 'self'; script-src 'self'; frame-ancestors 'none'; style-src 'self' 'unsafe-inline'; img-src 'self' data:;

Could you please help us take a look and advise?

Hi @maliming, Thanks for your prompt reply. if the CMS admin function is available in Angular UI, can guide me how to enable it?

However, I got another problem after adding CmsKit.Pro module, there is no update on the database level.

I know that the Angular UI is not supported for this module, but the administration and management CMS functions should be supported, right?

Hi @maliming, thanks, I realized that I had tried to add Cms.Kit module into an existing module template instead of application template.

This issue does not happens in application template.

• ABP Framework version: v5.2.2
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:"

Hi, I have tried to add the CMS Kit module into my existing solution but getting this error:

C:\Users\Admin\source\repos\AbpModuleTemplate>abp add-module Volo.CmsKit.Pro
[10:48:41 INF] ABP CLI (https://abp.io)
[10:48:41 INF] Version 5.2.2 (Stable)
[10:48:42 WRN] ABP CLI has a newer stable version 5.3.1, please update to get the latest features and fixes.
[10:48:42 WRN]
[10:48:42 WRN] Update Command:
[10:48:42 WRN] dotnet tool update -g Volo.Abp.Cli
[10:48:42 WRN]
[10:48:43 INF] Installing module 'Volo.CmsKit.Pro' to the solution 'AbpModuleTemplate'
[10:48:43 INF] Checking installed npm global packages...
Build started...
Build succeeded.
Your startup project 'AbpModuleTemplate.EntityFrameworkCore' doesn't reference Microsoft.EntityFrameworkCore.Design. This package is required for the Entity Framework Core Tools to work. Ensure your startup project is correct, install the package, and try again.

I am using the totally new startup template solution, no customization at all. any idea?

Thanks @maliming, so the tempkey.jwk is generated because Api.Host references to AbpIdentityServerDomain module, this file is not in used, right?

• ABP Framework version: v5.2.2
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:"

Hi, I have updated my IdentityServer project to not using the developer signing credential, the tempkey.jwk is not generated after that:

    public override void PreConfigureServices(ServiceConfigurationContext context)
    {
        // disable developer signing credential
        PreConfigure<AbpIdentityServerBuilderOptions>(options =>
        {
            options.AddDeveloperSigningCredential = false;
        });

        // add custom signing credential
        var cert = GetClientCertificate("cbc983009c08bc76cc2a61fc4a21349792d6452d");
        PreConfigure<IIdentityServerBuilder>(builder =>
        {
            builder.AddSigningCredential(cert);
        });
    }

However, the API project still keeps generating the tempkey.jwk file during the start up, anyone knows why and what is it using for?

• ABP Framework version: v3.3.2
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:"

Hi, I am upgrading our ABP framework from version 3.3.2 to 4.4.4 and found that new tables related to payment were added after executed add-migration command, below are the table names:

PayPaymentRequests, PayPlans, PayPaymentRequestProducts, PayGatewayPlans

Are these tables related to payment module? why do we need them? our solution does not have dependencies on payment module.

Hi, we have followed and override the JavaScript, it works now.

Thank you.