# Decode JWE's access token

**URL:** <https://community.auth0.com/t/decode-jwes-access-token/107508>\
**Category:** Get Help\
**Tags:** authentication-sessions, sessions\
**Created:** [May 22, 2023, 9:45am UTC](https://community.auth0.com/t/decode-jwes-access-token/107508 "2023-05-22T09:45:12Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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 26, 2023, 10:45pm UTC](https://community.auth0.com/t/decode-jwes-access-token/107508/3 "2023-05-26T22:45:58Z")

</div>

Hey there @kito.hirokazu welcome to the community!

> [@kito.hirokazu](#):
>
> {  
> “alg”: “dir”,  
> “enc”: “A256GCM”,  
> “iss”: “XXX”  
> }

This looks like an opaque access token - If you need to decode it at all, you’ll need to include an audience param when constructing the `/authorize` request. It depends on how you are initiating authorization, but the audience is typically set when configuring Auth0 - For example [AuthorizationParams](https://auth0.github.io/auth0-react/interfaces/AuthorizationParams.html#audience) in auth0-react.

The following FAQs should be of use:

[https://community.auth0.com/t/why-is-my-access-token-not-a-jwt-opaque-token/31028](https://community.auth0.com/t/why-is-my-access-token-not-a-jwt-opaque-token/31028)  
[https://community.auth0.com/t/what-is-the-audience/71414](https://community.auth0.com/t/what-is-the-audience/71414)

---

_[View the full topic](https://community.auth0.com/t/decode-jwes-access-token/107508)._
