# Basic question about resolving a token

**URL:** <https://community.auth0.com/t/basic-question-about-resolving-a-token/105758>\
**Category:** Get Help\
**Tags:** login-experience, new-universal-login-experience\
**Created:** [April 28, 2023, 4:17pm UTC](https://community.auth0.com/t/basic-question-about-resolving-a-token/105758 "2023-04-28T16:17:00Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [May 2, 2023, 9:00pm UTC](https://community.auth0.com/t/basic-question-about-resolving-a-token/105758/7 "2023-05-02T21:00:56Z")

</div>

Linking to the post below as I believe it answers this question as well:

> [@JWT token is "invalid signature"?](https://community.auth0.com/t/jwt-token-is-invalid-signature/105796/5):
>
> Hey @kkrp1 ! Again, this all comes down to the audience - This would be passed to getTokenSilently via [authorizationParams](https://auth0.github.io/auth0-spa-js/interfaces/GetTokenSilentlyOptions.html#authorizationParams). If the only thing you are doing is using the access token to call /userinfo then you are correct in that you do not need an audience, nor do you need to validate the token per se. In most cases, the access token is used to access an API (your API) and in that case you’d want a JWT to inspect which does require an audience (your API identifier in Auth0) as you’ve seen.

Hopefully this clears things up for you 🙂

---

_[View the full topic](https://community.auth0.com/t/basic-question-about-resolving-a-token/105758)._
