# Lock version update from 9 to 10

**URL:** <https://community.auth0.com/t/lock-version-update-from-9-to-10/8103>\
**Category:** Get Help\
**Tags:** lock-10\
**Created:** [September 6, 2017, 8:30am UTC](https://community.auth0.com/t/lock-version-update-from-9-to-10/8103 "2017-09-06T08:30:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![admin29](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@admin29](https://community.auth0.com/u/admin29)\
**Post date:** [September 6, 2017, 8:30am UTC](https://community.auth0.com/t/lock-version-update-from-9-to-10/8103/1 "2017-09-06T08:30:14Z")

</div>

I updated the Lock Client from version 9 to 10.

In my previous version of the code, defining a callback, example:  
"[https://www.site.com](https://www.site.com) ", I was able to login/signup from any url within my site “[https://www.site.com/page1](https://www.site.com/page1)” or “[https://www.site.com/page2](https://www.site.com/page2)” .  
Now with version 10, I found this impossible to do, any feedback??. What I dont want is redirect the page to the main URL to login/signup.

I am updating to version 10, because I would like add custom fields as part of user’s registration.

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [September 6, 2017, 3:14pm UTC](https://community.auth0.com/t/lock-version-update-from-9-to-10/8103/2 "2017-09-06T15:14:00Z")

</div>

As far as I’m aware there is nothing in Lock 10 that would prevent you to initiate a login/signup from any of the paths available in your web application. Depending on the configuration being used you you could need to provide a known `redirectUrl` (configured in the allowed callback URL’s of the associated client application) that would be where the end-user would be redirected after completing the authentication step. **However, the end-user would still be able to initiate the login from any path/page in the site**.

Without concrete information about the Lock configuration being used and additional context information about your specific end goal is almost impossible to provide a definitive answer. The recommendation would be for you to update your question with the additional information.

---

<div class="post-metadata">

**Author:** ![admin29](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@admin29](https://community.auth0.com/u/admin29)\
**Post date:** [September 7, 2017, 1:52am UTC](https://community.auth0.com/t/lock-version-update-from-9-to-10/8103/3 "2017-09-07T01:52:44Z")

</div>

Thank you for your response, let’s me provide more context information.  
Using this client version:

JS Code :  
const AUTH0\_CLIENT\_ID = ‘XXXXX’;  
const AUTH0\_DOMAIN = ‘[domain.auth0.com](http://domain.auth0.com)’;  
const AUTH0\_CALLBACK\_URL = window.location.href;  
const options = {  
allowedConnections: “custom-authentication”,“facebook”] // allowed two ways to sign in the application (facebook and custom)  
}  
//initializing the client  
const lock = new Auth0Lock( AUTH0\_CLIENT\_ID,AUTH0\_DOMAIN, options);

Auth0 Side, (Allowed Callbacks)

> **[Website Domain Names, Online Stores & Hosting - Domain.com](https://www.domain.com/)**
>
> Finding the perfect website domain is as easy as 1-2-3. Buy a domain name, build and host a website, and enjoy our professional online marketing tools.

IDK is this is enough, thank you for your assistance.

---

<div class="post-metadata">

**Author:** ![admin29](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@admin29](https://community.auth0.com/u/admin29)\
**Post date:** [September 7, 2017, 1:59am UTC](https://community.auth0.com/t/lock-version-update-from-9-to-10/8103/4 "2017-09-07T01:59:45Z")

</div>

Sorry for the previous comment, the format is weird.  
I used /lock/10.20.0/lock.min.js as client, I have two clients one using version 9, the other using version 10, it’s exactly same code, same configuration, even when I downgrade the suth0 client from 10 to 9 I can login/signup in any part of the site what it’s extremely weird. Maybe I need to add another parameter as part of configuration or I am missing something. I am using a custom database and facebook as login provider.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 2, 2018, 5:56am UTC](https://community.auth0.com/t/lock-version-update-from-9-to-10/8103/5 "2018-03-02T05:56:21Z")

</div>


