Authentication Issue on FF and Chrome

  • anortiz08

    (@anortiz08)


    8 years, 9 months ago

    With the latest WP-Members plugin 3.1.9.1, I am seeing inconsistent login behavior between browsers using the WP-Members login form. When a user attempts to authenticate on FF or Chrome via the WP-Members login form, the authentication request does not complete successfully on the initial attempt. If the use re-attempts the authentication request, they are then able to access the restricted content. If that same user authenticates via the native WordPress login form (/wp-login.php), the authentication request is successful on the initial attempt.

    Oddly, if the user attempts with MS Edge on the initial authentication request, the authentication request completes successfully and the user can access the restricted content. I am able to easily reproduce the issue but I cannot determine the root cause. I can create a video to demonstrate the issue but I noticed someone else has reported the same issue here: https://ww.wp.xz.cn/support/topic/login-module-not-working-properly/ . I should note that I did not experience this issue until the last WP-Members plugin update.

    ** As a side note, there is no server-side or WP caching in place. Just a base install of WP 4.8.1, Gantry 5 framework with the Helium theme, and WP-Members all running in Azure App Service.

Viewing 1 replies (of 1 total)
  • Plugin Author Chad Butler

    (@cbutlerjr)

    8 years, 9 months ago

    Based on what you’re describing, I would be surprised if this were the plugin or WP as the core of the issue. User authentication occurs server-side so it is not browser specific. The plugin uses wp_signon() (the WP authentication) to authenticate and log a user in, so it’s a core WP process.

    I know you said that there is no server side cache in place, but are you certain of this? What kind of container are you running in Azure? Do you know for sure that configuration does not include server side cache?

    You may wonder why I go back to that as a very possible issue. It’s because what you described is very much like a server side cache known as Varnish. Varnish must be configured with exceptions for cacheing things like login pages. When used with WP, often it will be pre-configured with exceptions for wp-login.php, but any “front end” login is not excepted. The behavior you described for FF and Chrome are exactly what is usually seen in this kind of case.

    So more needs to be known about what your Azure container actually contains, unless you totally scratch built the web service and know exactly what Apache (or other web server) modules are active and installed.

Viewing 1 replies (of 1 total)

The topic ‘Authentication Issue on FF and Chrome’ is closed to new replies.