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.
The template card payload is written into the notification property bag as JSON and read
back when the notification is published, but TemplateCard is abstract, so Newtonsoft.Json
could never restore it ("Could not create an instance of type ... abstract class") and the
card was lost as soon as the notification was persisted or queued for a retry.
- add TemplateCardJsonConverter and TemplateCardSystemTextJsonConverter, which resolve the
concrete card from the card_type discriminator (read from the constructor IL, falling back
to the type name) and reject an unknown discriminator
- split NotificationDataWeChatWorkExtensions into partials per message type (file, mini
program, mp news, template card, text card, video, voice) and add the shared
TryGetMessagePayload helper that deserializes with the converter
- add the Safe, EnableIdTrans, EnableDuplicateCheck and DuplicateCheckInterval switches
- migrate TuiJuheNotificationPublishProvider to the NotificationPublishContext contract the
other providers already use, and skip the interceptors for notifications at or above Warn
- bind the WeChat Work mini program account through the new work-weixin/miniprogram/bind
endpoint using the code2session user id
- rename AbpNotificationOptions to AbpNotificationsPublishOptions in the tests, fix the SMS
test project reference, retarget the templating tests to net10.0, register the webhook
notification projects and add the missing IP2Region reference
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