Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
To secure production enviornment from Brute force attack Odoo has implemented login_cooldown_after
It working fine when workers = 0
The moment i activate/ put worker >0 it does not work and did not produce failour count
as it not sharing login attempt counter between different process.
what is the alternative solution and is not possible to use login_cooldown_after in multithreading environment?
odoo stores logins trials in registry so you can not guarantee which worker(process) the user will try each time. the best solution suggested from odoo use tool like fail2ban
it means login_cooldown_after feature is useless!!
أنشئ حساباً اليوم لتستمتع بالخصائص الحصرية، وتفاعل مع مجتمعنا الرائع!
تسجيل
1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.
