| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 670 |
| Technical Name |
bf_login_recaptcha_lite |
| License | OPL-1 |
| Website | https://bugfree.com.br |
| Versions | 12.0 13.0 14.0 15.0 16.0 17.0 18.0 19.0 |

Bugfree Login reCAPTCHA Lite
Protect your Odoo login with Google reCAPTCHA. Set a failure threshold so the captcha only appears after N consecutive failed logins, or set 0 to always show it.
Better UX (like the big sites)
CAPTCHAs can annoy users and hurt conversion. With this module, your site behaves like large platforms (e.g., Amazon, Google, Microsoft, GitHub, Reddit): show challenges only when suspicious, such as after 2–3 failed attempts. Configure your own threshold in Settings.
Quick Setup
- Go to Settings → Login reCAPTCHA.
- Fill Site Key and Secret Key, and choose a Fail Threshold (e.g., 2 or 3).
- Restart Odoo and clear caches if assets are cached.
How to get your own Google reCAPTCHA keys
- Open the admin console: https://www.google.com/recaptcha/admin.
- Click + Create (or Create new site).
- Choose reCAPTCHA v2 → "I'm not a robot" Checkbox (this module renders v2 checkbox widgets).
- Set a label (any name you like, e.g., My Odoo Login).
- In Domains, add every hostname that will serve your Odoo login (e.g., example.com, www.example.com). For development, add
localhost. - Add additional owners if desired, accept the terms, and (optionally) enable alerts.
- Submit and copy the generated Site key and Secret key.
- Paste them in Settings → Login reCAPTCHA and save. Set your Fail Threshold (e.g., 2 or 3).
Tip: For staging/dev you can use Google's public test keys that work on any domain (including localhost):
Site key: 6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI
Secret key: 6LeIxAcTAAAAAGG-vFI1TnRWxMZNFuojJ4WifJWe
Post‑install
- Restart Odoo
- Clear browser/CDN caches; use
?debug=assetsand hard refresh
Vídeo (click to play)
Português (Brasil)
UX: o captcha incomoda o usuário; com este módulo, ele aparece só quando necessário (ex.: após 2 ou 3 erros seguidos), como fazem Amazon/Google/Microsoft/GitHub/Reddit.
Como obter suas próprias chaves
- Acesse https://www.google.com/recaptcha/admin.
- Clique em Create e selecione reCAPTCHA v2 → "I'm not a robot" Checkbox.
- Informe um rótulo e adicione os Domínios (ex.: example.com, www.example.com) e
localhostpara testes. - Salve e copie as chaves Site e Secret.
- No Odoo, vá em Configurações → Login reCAPTCHA, cole as chaves e defina o limiar de falhas (ex.: 2 ou 3).
Chaves públicas de teste (apenas desenvolvimento; funcionam também em localhost):
Site key: 6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI
Secret key: 6LeIxAcTAAAAAGG-vFI1TnRWxMZNFuojJ4WifJWe
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