You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After PR #635, an identity that is forgotten and later restored still ends the audit log on deprovisioned. Identity::restore() emits IdentityRestoredEvent, but Middleware does not map that event to an audit-log action and the event is also absent from AuditLogRepository::$secondFactorEvents.
Why this matters
For a live identity the terminal audit-log entry can read as if the account is still gone, because there is no matching restored entry after the earlier deprovisioned one.
Follow-up work
add IdentityRestoredEvent::class => "restored" to the audit-log action map in Middleware
include IdentityRestoredEvent in the audit-log query allowlist so the entry is visible to RA(A)s
add/update tests for projector + repository behavior
Problem
After PR #635, an identity that is forgotten and later restored still ends the audit log on
deprovisioned.Identity::restore()emitsIdentityRestoredEvent, but Middleware does not map that event to an audit-log action and the event is also absent fromAuditLogRepository::$secondFactorEvents.Why this matters
For a live identity the terminal audit-log entry can read as if the account is still gone, because there is no matching
restoredentry after the earlierdeprovisionedone.Follow-up work
IdentityRestoredEvent::class => "restored"to the audit-log action map in MiddlewareIdentityRestoredEventin the audit-log query allowlist so the entry is visible to RA(A)sReferences