Unfortunately, I only just discovered MainWP and am glad that I can use MainWP because it is nice and tidy.
Unfortunately, I discovered that the 1-click login doesn’t work for me because MainWP cannot bypass or trigger the 2FA from my security plugin “WP Login Lockdown”.
The message “No 2FA key found” always appears.
Can you please fix this in MainWP or get it working together with the developers of “WP Login Lockdown”?
Not only the users of your MainWP have the same problem, but also the users of ManageWP, which I have used so far but from which I now want to switch completely to you.
Thank you for your kind words! I’m glad you found us and to have you as part of the MainWP community.
Regarding the 1-click login issue you’re experiencing with the WP Login Lockdown plugin, it appears this is a specific case related to how that particular plugin handles 2FA. WP Login Lockdown requires a login process that includes a password entry to trigger the 2FA, while MainWP’s 1-click login bypasses that step since it doesn’t use login credentials directly so it will never trigger that email. If you are curious about how MainWP connects, we have a KB article for that here.
In these cases, we do not work to bypass or disable security measures users have in place for their websites.
This issue would need to be addressed on the WP Login Lockdown side to allow MainWP’s 1-click login to work seamlessly with their 2FA system. I encourage you to reach out to their development team, and we’d be happy to collaborate with them. They can contact us via MainWP.dev or our Developer Discord channel, and we’ll provide any necessary guidance.
Basically, I don’t want to weaken the security measures, but it would be practical if MainWP could perhaps check whether, for example, such a 2FA is set up on the MainWP dashboard and also on the MainWP client for the relevant user and then this user receives a green symbol after the previous 2FA on the dashboard page if he can be redirected, so to speak.
If he cannot be redirected, perhaps not the green symbol but a yellow symbol would be more useful and then the user is not redirected to the error message but directly to the login form where he can log in.
But thank you for wanting to get me excited about further development, where I will of course be happy to be available to you as a tester if I find the time. However, my current knowledge (in contrast to 20 years ago) is not sufficient to help you with further development.
I have already got into your Discord, but just because I have to rely on translators, I will not follow any chat histories there. If I want to know something from you, I can write it there or if you want to tell me something or if you want me to test something, you can let me know via PM.
No, I was a developer myself until almost 20 years ago. (Although 20 years is perhaps a bit of an exaggeration.)
It was only due to a lack of time that I was no longer able to keep up with the different languages and many innovations. (My time was when PHP3, PHP4 and PHP5 were current. But I tried to keep up with PHP7, but then I gave up.)
I only bought the WP Login Lockdown as a license, but others are developing it. I hope that the translator gets it across correctly this time.
Ah, I understand now, thank you. I also see your feature request
I’m not saying you have to do any development. It is something that needs to be handled on their end since we won’t do anything to get around their security features.
If the MainWP.dev site does not provide them enough information or if they have any issues doing this, we would need them to reach out to us, and we will be happy to help them, but without their active participation, there is not much we can do.
