Support » Plugin: Login by Auth0 » Did you updated the Legacy Lock API in latest version?

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

    (@auth0josh)

    Hi @ajayghaghretiya1,

    Version 3.4.0 should have updated you to the latest version of Lock at that time, 11.1 IIRC so if you’re on that version (or later) you should be fine. You can make sure by going to wp-admin > Auth0 > Settings > Advanced tab and see what you have under the “Lock JS CDN URL” (or “Widget URL” on older versions). If it says “11” anywhere in there, then you’re good to go! If not, change that to the latest:

    
    https://cdn.auth0.com/js/lock/11.7/lock.min.js
    

    Let me know if you have any trouble here!

    • This reply was modified 2 years, 4 months ago by Josh C.

    Hello Josh,

    Thanks for your meaningful replay.

    I have reviewed the advanced setting where I have found the URL
    //cdn.auth0.com/js/lock/10.7/lock.min.js

    So, here I have assumed that we need to update the plugin to the latest version of the plugin. Correct?

    After updating the plugin can we need to do any other changes for being not affected by the depreciation?

    Please do let me know your inputs about the same.

    Plugin Contributor Josh C

    (@auth0josh)

    You’re welcome!

    If you’re on a version less than 3.4.0 then a plugin update will help. If you’re already on the latest and that has not been adjusted for whatever reason, you can use the link I posted above. You can also use that new link with an older version of the plugin if you’re still testing the update (we definitely recommend you stay on the latest version).

    Hello Josh,

    Today Auth0 shut off the legacy endpoint, and our logins stopped working. They have a switch that allows us to use this old endpoint until August 6, but after that nobody will be able to log into our website. (I enabled this switch, so our site is fine right now.)

    I had hoped that updating to the latest plugin would fix this, but it hasn’t.

    We are using the latest version of the plugin(Version 3.6.2) and using the Lock js https://cdn.auth0.com/js/lock/11.5/lock.min.js.

    What do we need to do now? please suggest…

    Thanks,
    ajay

    Plugin Contributor Josh C

    (@auth0josh)

    > our logins stopped working

    Can you give me a little more detail here? Lock 11.x is the upgrade you’ll need and it sounds like you have that.

    https://auth0.com/docs/migrations/guides/legacy-lock-api-deprecation

    Hello Josh,

    I have not the Auth0 dashboard details but I have all the details about the Auth0 plugin details and website environment.

    Can we need to change anything from the Auth0 dashboard? or from the plugin to working with the new lock APIs.

    What details you need?

    Plugin Contributor Josh C

    (@auth0josh)

    You should not need to, no. That’s why I was asking about the login problems, what is the actual problem? Reproduction steps? Error messages?

    Hello Josh,

    I disabled the legacy API and tried to login, which gave me this:

    Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://thinkscience.au.auth0.com/co/authenticate. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://thinkscience.au.auth0.com/co/authenticate. (Reason: CORS request did not succeed).

    Please do let us know your inputs about the same.

    Thanks
    Ajay

    Plugin Contributor Josh C

    (@auth0josh)

    @ajayghaghretiya1 – It looks like we also have a support ticket open for this same issue. Do you want to continue here or on that ticket?

    A few things to check though:

    – Do you have you site’s domain set in the “Allowed Origins (CORS)” field for the Application you’re using?
    – Are you getting caught by anything related to cross-origin authentication, as explained here? It’s worth it to check another browser. We’re rolling out support for custom domains in the next release (not possible on a free plan, FYI).
    – Can you try using the latest Lock version? Change your JS CDN URL to https://cdn.auth0.com/js/lock/11.7/lock.min.js

    Hello Josh,

    Thanks for your detailed information about this issue.

    Yes, It would be great if you can provide us the URL of the ticket of Allowed Origins (CORS) Issue.

    Also, we will look into the settings that you have suggested.

    Thanks,
    Ajay

    Plugin Contributor Josh C

    (@auth0josh)

    The ticket I have for you is:

    https://auth0.zendesk.com/agent/tickets/45030 (not a public URL, must be logged in)

    Plugin Contributor Josh C

    (@auth0josh)

    One more thing to check … make sure your site’s domain is added to the “Allowed Web Origins” field as well. The plugin would not have worked before so it should be there but no reason not to check that as well.

    Feel free to respond here or on the ticket linked above if this is still a problem or if you found a fix.

    Hello Josh,

    We have fixed this issue by updating the Origins from Auth0 application. And It is working as expected.

    Thanks for your support.
    Ajay

    Plugin Contributor Josh C

    (@auth0josh)

    @ajayghaghretiya1 – great to hear, thanks for checking back in!

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Did you updated the Legacy Lock API in latest version?’ is closed to new replies.