Even though I've disabled 2FA at the host/tenant level, the option still shows up in the menu.
Related docs: ABP - Two-Factor Authentication (User Side) https://abp.io/docs/latest/modules/identity/two-factor-authentication#user-side
Can a multi-tenant Angular app support logging in to the same auth server from different domains, while preventing switching to other tenants? Below is my Angular dynamic-env.json configuration.
{ "production": true, "application": { "baseUrl": "https://{0}.koimpact.tw", "name": "Sroi" }, "oAuthConfig": { "issuer": "https://auth-imm.koimpact.tw/", "redirectUri": "https://{0}.koimpact.tw", "clientId": "Sroi_App", "responseType": "code", "scope": "offline_access Sroi", "requireHttps": true }, "apis": { "default": { "url": "https://api-imm.koimpact.tw", "rootNamespace": "Aws.Sroi" }, "AbpAccountPublic": { "url": "https://api-imm.koimpact.tw", "rootNamespace": "AbpAccountPublic" } } }
In case of a potential API key exposure, is it possible to reset the key? Also, what would be the impact on our live systems or those already deployed to client environments?
We typically divide the system into a backend and a public site, and use prefixes like AbpDistributedCacheOptions options.KeyPrefix = "MySitePublic:" to distinguish between different caches.
However, we’ve designed some FeatureDefinition configurations and use the SaaS feature system to manage tenant-specific functionality. The issue is that the public site’s cache doesn’t update immediately when these features change.
Are there any effective mechanisms to handle this problem—not just for Feature caching, but also for broader cache synchronization?
I want to get source @volosoft/ngx-lepton-x and @volo/ngx-lepton-x.core
After uploading an image, if the user later removes this image data, the blog or page will end up with many unused images. How do you handle this issue?
Version: ABP 9.2.0, using Angular UI and AuthServer.
What could be causing this problem?
If we move the generated files to another folder, we will lose the ability to use ABP Suite to add fields or make adjustments. This happens because we want to categorize folders using namespaces, for example, Abc/CMS/Pages/Page.cs. However, when generated by ABP Suite, it only creates the first-level folder Pages/Page.cs. After moving the folder, we lose the functionality of the CRUD Page Generator.
