# JWT access token invalid

**URL:** <https://community.auth0.com/t/jwt-access-token-invalid/9339>\
**Category:** Get Help\
**Tags:** jwt-validation, invalid, resource-owner-passw, access-token, access\
**Created:** [January 30, 2018, 8:23pm UTC](https://community.auth0.com/t/jwt-access-token-invalid/9339 "2018-01-30T20:23:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![muneebamughal](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@muneebamughal](https://community.auth0.com/u/muneebamughal)\
**Post date:** [January 30, 2018, 8:23pm UTC](https://community.auth0.com/t/jwt-access-token-invalid/9339/1 "2018-01-30T20:23:35Z")

</div>

I am integrating Auth0 with my backend application as an authorisation service. I have created an access token via endpoint `oauth/token` with client credentials and user’s email and password. Access token generated is verified by [jwt.io](http://jwt.io) with my custom API’s secret key. I am using HS256 and a custom api with identifier `http://localhost:4000/`. Also, guardian as the token decoding library which returns invalid token. My Guardian config:

```
config :my_app, MyApp.Guardian,
allowed_algos: "HS256"],
error_handler: Authentication.ErrorHandler,
issuer: AUTH0_DOMAIN,
verify_issuer: false,
secret_key: AUTH0_API_KEY
```

For token generation, I am using `http://localhost:4000/` as audience and `AUTH0_DOMAIN` as issuer, `grant_type`: password

I have spent so much time debugging My guardian implementation and testing with new APIs and Clients but couldn’t get it to work. What am I doing wrong?

Thank you so much for the help in advance. 🙂

---

<div class="post-metadata">

**Author:** ![priya.sharma.9362](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/priya.sharma.9362/32/14302_2.png) [@priya.sharma.9362](https://community.auth0.com/u/priya.sharma.9362)\
**Post date:** [February 5, 2018, 2:20pm UTC](https://community.auth0.com/t/jwt-access-token-invalid/9339/2 "2018-02-05T14:20:02Z")

</div>

Hi @muneebamughal,

Though I am not able to make a clear understanding on what the actual problem is, still I would suggest you to please check that if you are using the signing secret field of you API for validating the token.  
Please see [here][1]

And also make sure that you have configured the client and the API with the same signing algorithm.

---

<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, 9:55am UTC](https://community.auth0.com/t/jwt-access-token-invalid/9339/3 "2019-07-25T09:55:22Z")

</div>


