User Login Attempts Control
Prevent brute‑force attacks by locking out users after a configurable number of failed login attempts, ensuring your Odoo environment stays secure.
This security-focused Odoo module tracks every failed login attempt in your system and automatically locks the user account once a configurable threshold of failed attempts is reached. Administrators can easily monitor all attempts, identify suspicious login patterns, and manually reset the failed login counters to unlock users from the backend. Meanwhile, locked-out users see a clear, dynamic countdown timer on the standard Odoo login page informing them of when they can retry. All parameters, including maximum allowed failed attempts and lockout duration in seconds, are fully configurable from Odoo's settings panel without needing any custom code.
🛠️ Need Custom Feature? Customization Available!
We offer custom development and tailored features for this module starting at just $20 USD. Before purchasing, please discuss your specific customization requirements with us at markvaranval@gmail.com.
Key Advantages
Automatic Lockout
Users are automatically locked out after a configurable number of failed attempts, stopping brute‑force attacks.
Per‑User Tracking
Each user’s failed attempts are recorded individually, enabling precise security control.
Admin Reset
Administrators can manually unlock accounts directly from the Odoo backend.
Live Countdown Timer
A countdown timer on the login page informs users when they can try again.
Configurable Settings
Define maximum attempts and lockout duration from the Odoo settings UI.
Audit Log
Every failed attempt is recorded, providing a clear audit trail for security reviews.
Lightweight Front‑End
Uses a small vanilla‑JS script, adding virtually no load time to the login page.
No XML Changes Needed
Deployable as a standard Odoo addon without modifying existing views.
Multi‑Company Support
Works seamlessly across all companies in a multi‑company environment.
Improved Compliance
Helps meet security standards such as ISO 27001 by enforcing login attempt limits.
Installation Guide
- Extract Module: Unzip/Extract the downloaded module folder into your Odoo custom addons directory.
- Restart Server: Restart your Odoo server service to load the new addon path.
- Developer Mode: Log in to your Odoo database and activate the Developer Mode from the Settings dashboard.
- Update Apps List: Go to the Odoo Apps app, click on "Update Apps List" menu, and click Update.
-
Install Module: Search for
vits_user_login_attemptsorUser Login Attempts Controlin the Apps, and click Activate / Install. - Configuration Settings: Go to Settings -> General Settings, locate the "User Login Attempts Control" section to configure the maximum failed attempts and lockout duration.
Installed App
Successfully install and activate the "User Login Attempts Control" module from the Odoo Apps list.
Configuration Settings
Configure the maximum allowed failed login attempts and the lockout duration directly in settings.
Login Page Lockout Timer
A live countdown timer is displayed on the login page when login attempts are exceeded, preventing further inputs.
Full Working Demonstration
Watch the video showing the end-to-end functionality of login lockout and lockout timer.
Front‑End Lockout Timer
Displays a live countdown on the login screen, disabling input fields until the lockout period expires.
Backend Attempt Model
Stores each failed login with timestamp, user reference, and lockout expiry for precise control.
Configurable Limits
Admins can set the maximum number of failed attempts and lockout duration from the Settings menu.
Admin Manual Reset
Provides an action button to clear lockouts and reset attempt counters instantly.
Detailed Audit Log
Every failed attempt is recorded, enabling security audits and compliance reporting.
Zero‑Dependency JS
Implements the timer with pure vanilla JavaScript, avoiding extra library overhead.
Multi‑Company Ready
Works out‑of‑the‑box in multi‑company Odoo installations.
No XML Changes Required
Deploys as a standard add‑on without modifying existing Odoo views.
Multi Language Translation Available
We've included several languages out of the box. If your language is missing, simply contact us
and we'll provide a professional translation for free. We are committed to making our
tools accessible to everyone!
Drop us an email at: markvaranval@gmail.com
Chinese
French
German
Russian
Spanish
Arabic
You May Also Like
OUR EXPERTISE
— Get Support, For Free!
90 Days Free Support
In case of any bugs or issues (Except data recovery). We offer end-to-end solutions for Odoo services, from workflow analysis to integration.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module