# Preventing a Multiple Audiences Array

**URL:** <https://community.auth0.com/t/preventing-a-multiple-audiences-array/75327>\
**Category:** Get Help\
**Tags:** jwt, api, scope, aws-credentials, audience\
**Created:** [December 22, 2021, 11:49am UTC](https://community.auth0.com/t/preventing-a-multiple-audiences-array/75327 "2021-12-22T11:49:03Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![dan.woda](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dan.woda/32/18340_2.png) [@dan.woda](https://community.auth0.com/u/dan.woda)\
**Post date:** [December 23, 2021, 5:24pm UTC](https://community.auth0.com/t/preventing-a-multiple-audiences-array/75327/3 "2021-12-23T17:24:01Z")

</div>

Hi @jakub.tkac,

According to the following thread it looks like it is not possible.

> [@Access token has two audiences?](https://community.auth0.com/t/access-token-has-two-audiences/71041/3):
>
> Hey @woeterman94 , You cannot remove the /userinfo audience. It is included by default for all issued Access Tokens. If you specify an audience of your custom API identifier and a scope of openid, then the resulting access token’s aud claim will be an array rather than a string, and the access token will be valid for both your custom API and for the /userinfo endpoint. Other than in the use case of a single custom API as well as Auth0’s /userinfo endpoint, your access tokens will be unable to …

---

_[View the full topic](https://community.auth0.com/t/preventing-a-multiple-audiences-array/75327)._
