Authentification - Brute-Force Filterby GRAP https://github.com/OCA/server-tools , Tecnativa https://github.com/OCA/server-tools , Odoo Community Association (OCA) https://github.com/OCA/server-tools
|Also available in version||v 11.0 v 9.0|
Tracks Authentication Attempts and Prevents Brute-force Attacks
This module registers each request done by users trying to authenticate into Odoo. If the authentication fails, a counter is increased for the given remote IP. After a defined number of attempts, Odoo will ban the remote IP and ignore new requests. This module applies security through obscurity (https://en.wikipedia.org/wiki/Security_through_obscurity), When a user is banned, the request is now considered as an attack. So, the UI will not indicate to the user that his IP is banned and the regular message 'Wrong login/password' is displayed.
This module realizes a call to a web API (http://ip-api.com) to try to have extra information about remote IP.
You can use these configuration parameters that control this addon behavior:
- auth_brute_force.whitelist_remotes is a comma-separated list of whitelisted IPs. Failures from these remotes are ignored.
- auth_brute_force.max_by_ip defaults to 50, and indicates the maximum successive failures allowed for an IP. After hitting the limit, the IP gets banned.
- auth_brute_force.max_by_ip_user defaults to 10, and indicates the maximum successive failures allowed for any IP and user combination. After hitting the limit, that user and IP combination is banned.
Admin user have the possibility to unblock a banned IP.
This module generates some WARNING logs, in the following cases:
- When the IP limit is reached: Authentication failed from remote 'x.x.x.x'. The remote has been banned. Login tried: xxxx.
- When the IP+user combination limit is reached: Authentication failed from remote 'x.x.x.x'. The remote and login combination has been banned. Login tried: xxxx.
List of Attempts
For further information, please visit:
Known issues / Roadmap
- Remove 🐒 patch for https://github.com/odoo/odoo/issues/24183 in v12.
- Depending of server and / or user network configuration, the idenfication
of the user can be wrong, and mainly in the following cases:
- If the Odoo server is behind an Apache / NGinx proxy and it is not properly configured, all requests will use the same IP address. Blocking such IP could render Odoo unusable for all users! Make sure your logs output the correct IP for werkzeug traffic before installing this addon.
- The IP metadata retrieval should use a better system. See details here.
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smash it by providing detailed and welcomed feedback.
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
To contribute to this module, please visit https://odoo-community.org.
Please log in to comment on this module
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.