Skip to content

fix(whitelist): always allow intrusion detection's login confirmation - #1735

Draft
karlitschek wants to merge 1 commit into
mainfrom
fix/allow-intrusion-detection-confirmation
Draft

karlitschek wants to merge 1 commit into
mainfrom
fix/allow-intrusion-detection-confirmation

Conversation

@karlitschek

Copy link
Copy Markdown
Member
  • Resolves:

Summary

Checklist

  • Code is properly formatted
  • Sign-off message is added to all commits
  • Tests are included where the change has logic
  • Screenshots before/after for front-end changes
  • Documentation has been updated or is not required

AI (if applicable)

  • The content of this PR was partly or fully generated using AI (Claude Code, claude-opus-5-5); every commit carries an Assisted-by trailer.

🤖 Generated with Claude Code

@karlitschek
karlitschek force-pushed the fix/allow-intrusion-detection-confirmation branch 4 times, most recently from 6b6b91a to f40f741 Compare October 22, 2026 16:39
The intrusion_detection app holds a suspicious login on its own pages
until it is confirmed, for example with a code sent by email. Guests
answered those pages with a 403 unless an administrator had whitelisted
the app, so a guest asked to confirm a login was stuck with no way
forward. Like the two-factor apps, it is now always allowed.

Assisted-by: ClaudeCode:claude-opus-5-5
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Frank Karlitschek <karlitschek@users.noreply.github.com>
@karlitschek
karlitschek force-pushed the fix/allow-intrusion-detection-confirmation branch from f40f741 to e060d58 Compare October 22, 2026 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant