# Could someone clarify what exactly client.isAuthenticated() does?

**URL:** <https://community.auth0.com/t/could-someone-clarify-what-exactly-client-isauthenticated-does/138293>\
**Category:** Get Help\
**Tags:** login-experience, new-universal-login-experience\
**Created:** [July 7, 2024, 1:54pm UTC](https://community.auth0.com/t/could-someone-clarify-what-exactly-client-isauthenticated-does/138293 "2024-07-07T13:54:03Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![mhmh33usas](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@mhmh33usas](https://community.auth0.com/u/mhmh33usas)\
**Post date:** [July 7, 2024, 1:54pm UTC](https://community.auth0.com/t/could-someone-clarify-what-exactly-client-isauthenticated-does/138293/1 "2024-07-07T13:54:03Z")

</div>

I’m fairly new to JWTs. I’m trying to understand what happens on the client vs. what happens on the server.

The function `client.isAuthenticated()` is part of the front end SDK. So my quesiton is, how can the front end possibly determine if the user is authenticated - surely that’s something that should be trusted only to the back end, via something like [jose](https://github.com/panva/jose)’s `jwtVerify()`.

Is it simply that the front end can determine (only) that the passed code is “valid” i.e. not expired, but cannot actually determine whether it represents an authenticated user (which is a back end job), or am I way off?

Thank you in advance.

---

_[View the full topic](https://community.auth0.com/t/could-someone-clarify-what-exactly-client-isauthenticated-does/138293)._
