📝 Preliminary Checks

• I tried searching for an existing issue and followed the debugging docs advice, but still need assistance.

👀 What Happened?

with OAUTH2 enabled, sign-in with Roundcube is successful, however, the client IP is eventually banned by fail2ban.

The reason is because !include auth-oauth2.conf.ext comes after !include auth-passwdfile.inc.

Simply moving !include auth-oauth2.conf.ext above !include auth-passwdfile.inc is enough to prevent a ban, however, there was some discussion on the PR related to other issues with the ordering.

👟 Reproduction Steps

enable OAUTH2, enable fail2ban, sign in to account with OAUTH2, wait for fail2ban to trigger because regular passdb lookup fails before oauth2 is used.

🐋 DMS Version

v13.3.0

💻 Operating System and Architecture

Fedora CoreOS

⚙️ Container configuration files

No response

📜 Relevant log output

No response

Improvements to this form?

No response