• Resolved tqsitdept

    (@tqsitdept)


    I am having a two-part problem on our company intranet site:

    1) We are currently on Login by Auth0 3.5.2. Any time since that version that I’ve tried to update, users get an invalid state error when logging in. Auth0 error log shows the following: WP_Auth0_Api_Client::search_connection
    N/A
    {“statusCode”:401,”error”:”Unauthorized”,”message”:”Expired token received for JSON Web Token validation”,”attributes”:{“error”:”Expired token received for JSON Web Token validation”}}

    2) In troubleshooting that issue, while still logged in after updating Login by Auth0 to 3.10.0, I tried changing certain settings (such as turning the custom Lock URL off). However, when clicking the Save Changes button, nothing happens. Tested this issue in both Chrome and Edge.

    I believe if the Save Changes button issue were resolved, I might be able to resolve the first problem on my own, but I can’t say for sure without the ability to test changes.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Josh C

    (@auth0josh)

    Sorry for the trouble here @tqsitdept. Happy to help figure it out.

    Any time since that version that I’ve tried to update, users get an invalid state error when logging in.

    State validation was added in 3.6.0, which explains why 3.5.2 is working fine but nothing later than that:

    https://github.com/auth0/wp-auth0/releases/tag/3.6.0

    We have a thorough guide to troubleshooting this issue here:

    https://auth0.com/docs/cms/wordpress/invalid-state

    However, when clicking the Save Changes button, nothing happens.

    That’s odd. I build everything in Chrome and have not seen this issue. There isn’t any JS tied to that form submitting so I can’t think of what would cause that to happen. Can you open your JS Console in Chrome and see if any errors appear?

    Thread Starter tqsitdept

    (@tqsitdept)

    We do use WPEngine, so I was able to contact them to have the cache exclusions added as described in your support article, which seems to have resolved issue 1.

    I had to wait until this point to check the JS Console for issue 2 again, as we had rolled back the site in the meantime. Now that issue 1 is resolved, I’m unable to reproduce the second issue with the Save Changes button. Unless it could have been related to caching as well, I have no clue what happened there.

    At any rate, all our problems have gone away. Thanks for your help with this!

    Plugin Contributor Josh C

    (@auth0josh)

    Happy to help! Please post back if you have any issues upgrading. We have another release about to go out as well if you want to wait a few days to get that one in as well.

    Plugin Contributor Josh C

    (@auth0josh)

    Just a quick update here … we found an issue with saving changes on the settings page (an invalid URL in the custom CDN URL would cause a console error in Chrome but, otherwise, not allow saving). We fixed that in 3.11.1, released today!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Cannot click “Save changes” button in WP admin portal Auth0 Settings’ is closed to new replies.