Release 1.3.1 #6
No reviewers
Labels
No labels
priority
high
priority
low
priority
medium
priority
none
resolution
done
resolution
wontfix
status
in-progress
status
in-review
type
bug
type
enhancement
type
refactor
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
renekreijveld/jfail2ban!6
Loading…
Reference in a new issue
No description provided.
Delete branch "develop"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Release 1.3.1: develop into main.
Fixed
A failed passkey login ("Log in with a passkey", plg_system_webauthn) already triggered onUserLoginFailure and was logged as LOGINFAIL, but with an empty username (user=-): the passkey plugin passes an empty authentication response. The plugin now takes the user from the session (plg_system_webauthn.userId, set by the challenge request and cleared only after the failure event). Without a challenge for an existing user it stays user=-. A passkey used as the second factor (MFA) whose signature does not verify was already logged as MFAFAIL; the README now says so. Tested in DDEV with invalid passkey assertions: login after a challenge for admin (user=admin), login without a challenge (user=-), and the passkey MFA method (MFAFAIL, try counter of the passkey record raised). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>