# How to refresh sessions when upgrading to lock 11?

**URL:** <https://community.auth0.com/t/how-to-refresh-sessions-when-upgrading-to-lock-11/9683>\
**Category:** Get Help\
**Created:** [March 3, 2018, 8:12am UTC](https://community.auth0.com/t/how-to-refresh-sessions-when-upgrading-to-lock-11/9683 "2018-03-03T08:12:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kevinauth](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@kevinauth](https://community.auth0.com/u/kevinauth)\
**Post date:** [March 3, 2018, 8:12am UTC](https://community.auth0.com/t/how-to-refresh-sessions-when-upgrading-to-lock-11/9683/1 "2018-03-03T08:12:42Z")

</div>

We are upgrading to lock 11 (from 9), where we previously used getClient().refreshToken. We are wondering how to do the same in lock 11. It looks like there is a checkSession method from the auth0 library, but it’s not clear how to leverage authentication from lock, and checkSession from auth0. Is this possible?

We tried a few different things, and the current error we get during checkSession() is “Error: accessToken parameter is not valid”. This is after logging in successfully with lock. Is there some way to hand the auth info from lock over to auth0.js?

---

<div class="post-metadata">

**Author:** ![jerdog](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jerdog/32/11231_2.png) [@jerdog](https://community.auth0.com/u/jerdog)\
**Post date:** [March 3, 2018, 11:43pm UTC](https://community.auth0.com/t/how-to-refresh-sessions-when-upgrading-to-lock-11/9683/2 "2018-03-03T23:43:24Z")

</div>

Have you had a look at the [Lock v11 API reference](https://auth0.com/docs/libraries/lock/v11/api)? This [migration guide](https://auth0.com/docs/libraries/lock/v11/migration-guide) also might have some helpful info to connect the dots

---

<div class="post-metadata">

**Author:** ![kevinauth](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@kevinauth](https://community.auth0.com/u/kevinauth)\
**Post date:** [March 4, 2018, 2:34am UTC](https://community.auth0.com/t/how-to-refresh-sessions-when-upgrading-to-lock-11/9683/3 "2018-03-04T02:34:01Z")

</div>

Thanks, but so far I haven’t seen any information about using lock and also Auth0.js together. This makes migration extremely difficult from older versions of lock, when needing session refresh.

---

<div class="post-metadata">

**Author:** ![richard.dowinton](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/richard.dowinton/32/16150_2.png) [@richard.dowinton](https://community.auth0.com/u/richard.dowinton)\
**Post date:** [March 5, 2018, 7:53am UTC](https://community.auth0.com/t/how-to-refresh-sessions-when-upgrading-to-lock-11/9683/4 "2018-03-05T07:53:10Z")

</div>

The error you’re receiving should only occur if you call `userInfo` without specifying an access token.

Would you be able to share the code you’re using along with a [HAR file](https://auth0.com/docs/support/troubleshooting-with-har-files) (please remove any sensitive details such as password) so we can have a closer look at what’s going on?

Please upload both to a cloud storage service (e.g. Google drive), and share the link with us. Feel free to restrict access to the link for only `@auth0.com` email addresses using [Sharelock.io](http://Sharelock.io).

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [July 25, 2019, 11:03am UTC](https://community.auth0.com/t/how-to-refresh-sessions-when-upgrading-to-lock-11/9683/5 "2019-07-25T11:03:34Z")

</div>


