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
The QR code token grant trusted a client supplied tenant_id to switch the tenant context
before loading the user, so any caller could resolve a user id under an arbitrary tenant,
and the security events were logged under the generic login actions, which made a QR code
login indistinguishable from a password login in the audit trail.
- drop the tenant_id request parameter and use the tenant carried by the QR code itself
(QrCodeInfo.TenantId, taken from the scanning user's tenant)
- add QrCodeLoginSucceeded / QrCodeLoginFailed to IdentitySecurityLogExtendActionConsts and
use them from the QR code grant and the scan login page, including the failure log that was
missing when the user token does not match
- fix the invalid token branch, which logged LoginLockedout although the account was not
locked out; the real lockout branch keeps LoginLockedout
- update the README: correct grant_type=qr_code, document qrcode_key and drop the parameters
the flow no longer accepts (password, enterpriseId, the two factor and password change ones)
- register LINGYUN.Abp.OpenIddict.QrCode in the solution
BREAKING CHANGE: the QR code token request no longer accepts a tenant_id parameter; the tenant
is taken from the QR code. Clients that relied on passing tenant_id must drop it.
configureawait.props now provides the ConfigureAwait weaver through the Fody 6.9.3
WeaverConfiguration property and sets FodyGenerateXsd=false, so the per-project
FodyWeavers.xml files and every FodyWeavers.xsd are redundant.
- delete 450 FodyWeavers.xml and 438 FodyWeavers.xsd from the framework, modules,
services, gateways, tests and migrations projects and from the micro service template
- every removed FodyWeavers.xml was equivalent to the default supplied by configureawait.props
(439 x <ConfigureAwait ContinueOnCapturedContext="false" />, 20 x <ConfigureAwait />, whose
default is ContinueOnCapturedContext=false, and 2 of those with an XML declaration); no
Blazor / AspNetCore.Components project carried one and the template manifests do not list them
- the aio template keeps its 22 files: its own Directory.Packages.props pins Fody 6.8.0, which
does not support the WeaverConfiguration property
- Session policy processing is transferred to the identity auth service
- Add an identity authentication job module
- Add an expired session cleaning job
- update `common.props`
- update `Directory.Packages.props`
- Use `MyCSharp.HttpUserAgentParser` to replace `DeviceDetector.NET` for better performance