Two-factor Authentication for Custom Login Page

  • Resolved hecttech08

    (@hecttech08)


    4 years ago

    Hello,

    New to asking questions on here.

    My website has a custom login page that I created. It also prevents you from trying to access the standard wp-login page by redirecting you back to the custom login page.

    I was testing using SG Security Plugin’s Two-Factor Authentication on my staging site. When I turn on 2FA, I get a parse error when trying to log into my staging site on multiple browsers. Since it prevents me to log back onto the website, I have to log back in through siteground directly to get back to the admin panel.

    I confirmed If I turn off 2FA, and log out, I can log back onto the staging site like normal.

    I then tried to turn off a feature I have in place to prevent logging directly to wp-login page. This way I can test 2fa on my staging site from there. 2FA works perfectly when you go to wp-login page. Prompts you to set up with your phone and everything works.

    So I guess after all this testing, my question is the following:

    Will SG Security Plugin’s Two-Factor Authentication work for Custom Login Pages?

    Are there any shortcodes or anything I can use to add to an Elementor page in order for my custom login page to see the props for codes/authenticator set up?

    I’m assuming the parse error is shown because the custom login page is waiting for a response after you enter the email and password. But it’s expecting more info to be entered. Whether it’s setting up 2fa or entering the code itself.

    Any way around this?

    • This topic was modified 4 years ago by hecttech08.
Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Plamen M

    (@plamenm)

    4 years ago

    Hello @hecttech08 ,

    After you enable the 2FA through our plugin, try flushing all of available caching – the SiteGround Optimizer, any cache kept in your theme or another plugin as well as the server sided caching and the local browser cache.

    If this does not help, provide us with the exact parse error that is shown and also check if the browser’s debug console shows any error and provide us with it too.

    We look forward to your reply.

    Regards,
    Plamen.M
    Tech Support Team
    SiteGround.com

    Thread Starter hecttech08

    (@hecttech08)

    4 years ago

    Hello,

    Thank you for responding.

    I just tested this. I cleared local and server cache.

    Tried again on multiple browsers, same issue.

    Also, weird thing is, I had no errors on Chrome debug browser. However, the Firefox browser showed warning/errors. I will post it below. Keep in mind, there are characters missing, looks like it’s a unique identifier for my username. So I won’t add that part.But should be enough for what is going on, or what is expected. 

    Cookie “buddyboss_user_sw_has been rejected because it is already expired. admin-ajax.php
Cookie “buddyboss_user_sw_secure_ has been rejected because it is already expired. admin-ajax.php
Cookie “buddyboss_user_sw_olduser_ has been rejected because it is already expired. admin-ajax.php
Cookie “wordpress_ has been rejected because it is already expired. admin-ajax.php
Cookie “wordpress_sec_ has been rejected because it is already expired. admin-ajax.php
Cookie “wordpress_ has been rejected because it is already expired. admin-ajax.php
Cookie “wordpress_sec_has been rejected because it is already expired. admin-ajax.php
Cookie “wordpress_logged_in_ has been rejected because it is already expired. admin-ajax.php
Cookie “wordpress_logged_in_ has been rejected because it is already expired. admin-ajax.php
Cookie “wp-settings-0” has been rejected because it is already expired. admin-ajax.php
Cookie “wp-settings-time-0” has been rejected because it is already expired. admin-ajax.php
Cookie “wordpress has been rejected because it is already expired. admin-ajax.php
Cookie “wordpress has been rejected because it is already expired. admin-ajax.php
Cookie “wordpress_sec has been rejected because it is already expired. admin-ajax.php
Cookie “wordpress_sec has been rejected because it is already expired. admin-ajax.php
Cookie “wordpressuser has been rejected because it is already expired. admin-ajax.php
Cookie “wordpresspass has been rejected because it is already expired. admin-ajax.php
Cookie “wordpressuser has been rejected because it is already expired. admin-ajax.php
Cookie “wordpresspass” has been rejected because it is already expired. admin-ajax.php
Cookie “wp-postpass has been rejected because it is already expired.
    Plugin Support Pavel Dosev

    (@pdosev)

    4 years ago

    Hello @hecttech08,

    I am afraid that I cannot recreate the error on my end, and the parse from the debug log isn’t sufficient.

    If your website is hosted with Siteground, could you please provide us with its URL so that we can check and recreate the problem on a staging site and see what is causing it?

    Thread Starter hecttech08

    (@hecttech08)

    4 years ago

    Yes, Siteground is my host.

    https://www.staging2.collectahobby.com/login-page/

    That is the staging site Url. Please let me know if you would like me to create an account for you to test as well.

    Thanks again.

    Plugin Support Pavel Dosev

    (@pdosev)

    4 years ago

    Thank you, @hecttech08,

    I was able to recreate the issue on my end. I passed the information to our developers for further review, and once we have an update from them, we will update the thread to let you know.

    Thread Starter hecttech08

    (@hecttech08)

    4 years ago

    Ok great.

    Thank you for all of your help.

    I will be waiting for a response.

    If you need me to try something new, just let me know.

    Thread Starter hecttech08

    (@hecttech08)

    4 years ago

    Hello,

    I was just curious if there has been any progress on a solution for the issues I have with 2fa on a custom Login page?

    Plugin Support Gergana Petrova

    (@gpetrova)

    4 years ago

    Hello @hecttech08,

    Our developers are still looking into the issue at hand. As soon as there’s any progress – we will post an update to the topic.

    Since the issue was already reported internally, we will mark the topic as resolved, however you will still be able to post new replies if needed.

    Best Regards,
    Gergana Petrova

    Plugin Support Pavel Dosev

    (@pdosev)

    3 years, 11 months ago

    The page you were using on your site was not created using the Elementor’s custom login page widget (which is part of the premium version of Elementor), and the problem you are facing is a specific one for your custom theme and that page.

    You can try using Elementor’s custom login page with which our 2FA works correctly.

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Two-factor Authentication for Custom Login Page’ is closed to new replies.

Tags