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.
Both reset buttons invalidate the user's two-factor credentials, so render them with the
danger style to signal the consequence before the confirmation dialog appears.
- apply danger to the reset authenticator button
- apply danger to the reset recovery code button
- show how many recovery codes are still available once the authenticator is enabled
- let the user reset the recovery codes, display the new list once and refresh the count
- add getRecoveryCodeCountApi and resetRecoveryCodeApi to useProfileApi, together with the
AuthenticatorRecoveryCodeCountDto type
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