Thanks @maliming, so the tempkey.jwk is generated because Api.Host references to AbpIdentityServerDomain module, this file is not in used, right?
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?
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.
Hi, we are hosting our Identity Server in IIS under a virtual application with the path: /identity/*
and we got the 404 not found when calling the switch tenant popup, we found that it calls the url **/Abp/MultiTenancy/TenantSwitchModal **instead of /identity/Abp/MultiTenancy/TenantSwitchModal due to the code below:
var tenantSwitchModal = new abp.ModalManager(abp.appPath + 'Abp/MultiTenancy/TenantSwitchModal');
May I know how to fix the issue?
Hi, can we use the ABP Framework v4.x to v5.0 Migration Guide to upgrade v4.0 to v5.0 directly and skip the 4.x to 4.2 and 4.2 to 4.3 upgrades?
Hi, there seemed to be missing ABP Framework Migration Guide from version 5.0 to 5.1
https://docs.abp.io/en/abp/latest/Migration-Guides/Index
Can you advice?
Hi, our current version is v3.3.2. We are not upgrading to the latest version just yet. And we need to address this vulnerability asap. Can you confirm on this, please?
Hi, can we confirm that the following is the security fix for Cross-Site Scripting vulnerability in the jquery-form 4.3.0 ?
The fixed version is available here: https://github.com/jquery-form/form/pull/586/files
Hi @gterdem, any update on this?