Hi,
Since the main purpose of NinjaFirewall protection is to work before WordPress is loaded, I don’t think it will be suitable. It could of course be implemented at the plugin level, but it seems there are already plugins doing that.
“It could of course be implemented at the plugin level, but it seems there are already plugins doing that.”
what do you mean?
You cannot implement it at the firewall level, because it is loaded before WP. It does not even know what WP is.
It could be added to the plugin which is used to configure the firewall from your admin dashboard.
I’m sorry, I still don’t understand your answer. Clef has a WP plugin and it works or replaces the wp-login area with their software.
Anthony
Sorry for the misunderstanding.
The login protection code is in the firewall part of NinjaFirewall, and it is triggered at the earliest stage (even before the firewall loads its own configuration).
If we wanted to implement a 2 factor authentication, it could only be done at the plugin level, not the firewall level. But because there is already a Clef plugin, our code would not bring any improvement, it would be 100% identical to their plugin.
No worries. 🙂
“But because there is already a Clef plugin, our code would not bring any improvement, it would be 100% identical to their plugin.”
So are you saying, it’s ok to use both? Since Clef is already built, I can use both NinjaFirewall and Clef plugin together?
I did not try it, but I think you can use both.
NinjaFirewall protects access to the wp-login.php script. It does not check how you authenticate yourself.
If you see a problem while using both, just report it here and I’ll have a look.
