Delete the modules/operation-rate-limiting projects and their EF Core/application tests, remove InvalidateCacheAsync from the dynamic policy store, and update the error code namespace, localization keys and documentation to the framework-only layout.
Add LINGYUN.Abp.OperationRateLimiting.Abstractions for models, attributes, enums and constants, keep the interfaces in the core package, remove the Redis state accessor in favor of rule reset/release services, align the management rule records, and split the tests into core, EF Core, application and Redis projects.
Use conventional DI for the static policy store, null dynamic store, Redis executor and Redis state accessor instead of explicit service registrations; rename the options-backed static store to StaticOperationRateLimitingPolicyStore.
Remove IOperationRateLimitingStore and the algorithm switch. Rules now own the algorithm logic and use IOperationRateLimitingStateAccessor for state, with Redis Lua rule implementations and a CAS state accessor.
Pick up the new profile recovery code endpoints and the renamed registration methods in the
account-generate-proxy.json snapshot, so the generated API description matches the
controllers again.
RegisterAsync was overloaded for the phone and the WeChat flow, so the client proxy and the
API description could not tell from the name which flow a call belonged to.
- rename RegisterAsync(PhoneRegisterDto) to PhoneRegisterAsync and
RegisterAsync(WeChatRegisterDto) to WeChatRegisterAsync in IAccountAppService,
AccountAppService and AccountController
- regenerate AccountClientProxy for the new names, the HTTP routes are unchanged
BREAKING CHANGE: the IAccountAppService.RegisterAsync overloads were renamed to
PhoneRegisterAsync and WeChatRegisterAsync. Consumers that call the application service or
the client proxy directly must update the call; the HTTP endpoints keep their routes.
A user could generate recovery codes once but never see how many were left or replace
them, so a lost or partly consumed code list could not be recovered.
- add AuthenticatorRecoveryCodeCountDto carrying the configured and the still available
number of codes
- add GetRecoveryCodeCountAsync and ResetRecoveryCodeAsync to IMyProfileAppService,
MyProfileAppService and MyProfileController, served as GET recovery-code-count and
PUT reset-recovery-code
- generate the codes with the configurable count instead of the hardcoded 10
- drop the redundant UserStore.ReplaceCodesAsync call, since
GenerateNewTwoFactorRecoveryCodesAsync already replaces the stored batch
- add the matching profile client proxy methods and localize the new messages
The number of two-factor recovery codes was hardcoded to 10 in the profile service and in
the two-factor page, so a deployment could not adjust it.
- replace the unused UseCaptcha constant, whose value pointed at ProhibitDefaultAdminRole
instead of a captcha setting, with GenerateRecoveryCodeNumber
- add the Security.GenerateRecoveryCodeNumber setting, defaulting to 10, for the default,
configuration, global and tenant value providers
- add IdentityTwoFactorBehaviourSettingHelper.GetGenerateRecoveryCodeNumber and use it from
the two-factor page instead of the literal
- localize the setting display name and description in en and zh-Hans
- Re-add ImplicitUsings, NSubstitute and Volo.Abp.Autofac that upstream
BlobContainerAuthorizationTests depends on, so the merged test project compiles
- Regenerate the CLI api description from the blob-management module so it matches
the module snapshot and no longer exposes TenantId
- The previous snapshot was host-wide and carried 520 unrelated types (Elsa,
System.Reflection, Asp.Versioning); the controller/action surface is unchanged (31)
- Remove the stale TenantId parameter and property of BlobDownloadByNameInput from
the CLI api-description snapshot so it matches the updated contract DTO
- Regenerate the CLI api description from the blob-management module so it matches
the module snapshot and no longer exposes TenantId
- The previous snapshot was host-wide and carried 520 unrelated types (Elsa,
System.Reflection, Asp.Versioning); the controller/action surface is unchanged (31)
- Remove the stale TenantId parameter and property of BlobDownloadByNameInput from
the CLI api-description snapshot so it matches the updated contract DTO
- Add LINGYUN.Abp.BlobManagement.EntityFrameworkCore.Tests with an in-memory EF host
and repository tenant-isolation tests
- Add LINGYUN.Abp.BlobManagement.Application.Tests covering tenant isolation,
resource-level authorization and download-key round trips
- Extend the domain tests with time-window, tampering, expiration and lifetime cases
- Register the new test projects in the solution
- Add the IBlobDownloadKeyGenerator abstraction, BlobDownloadKey and the default
HmacBlobDownloadKeyGenerator implementation
- Sign version, blob id, tenant id and expiration with HMAC-SHA256, verify with a
fixed-time comparison and accept canonical Base64Url encodings only
- Bucket the expiration by DownloadKeyWindow so the same key is generated within a
window and stays valid for at least DownloadKeyLifetime
- Add DownloadKeySecret/DownloadKeyLifetime/DownloadKeyWindow options, falling back to
the application encryption passphrase, and drop the global download key cache
- Remove the client-controlled TenantId from BlobDownloadByNameInput and drop the
download/by-name/t/{tenantId}/{name} route
- Do not switch the tenant from request data in BlobAppService; the policy check now
enforces the functional permission and the container/resource policy together
- Route id-based download, delete and download-url generation through the container
policy so resource grants of the users container cannot be bypassed
- Add a blob tenant ownership check and resolve storage of by-key downloads in the
tenant carried by the key
Keep the Elsa UserTask TagsJson column as text and convert the tags through a JSON value converter. This avoids Npgsql 10 mapping the collection to text[] while the Elsa migration still creates a text column.
The shared configureawait.props already supplies the ConfigureAwait weaver configuration for these assemblies, so the per-project FodyWeavers.xml/xsd files are redundant and no longer need to be tracked.
Elsa 3.9 passes CONCAT directly to THROW, which SQL Server rejects. Provide an idempotent repair script that creates the label and secret unique indexes and records the affected migrations.
Move Quartz property binding into AbpQuartzSqlInstallerModule so the migrator and service use the same installer configuration. Align provider connection names, set the QRTZ_ table prefix, and quote the SQL Server database name when creating it.
Elsa 3.9 already maps UserTask TagsJson to text. Forcing the property to text[] made Npgsql fail when reading tags, so use the provider's default mapping instead.