# Passed Audience is automatically overwritten during /authorize

**URL:** <https://community.auth0.com/t/passed-audience-is-automatically-overwritten-during-authorize/96106>\
**Category:** Get Help\
**Tags:** apis, application\
**Created:** [December 9, 2022, 9:58am UTC](https://community.auth0.com/t/passed-audience-is-automatically-overwritten-during-authorize/96106 "2022-12-09T09:58:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![admin61](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/admin61/32/33201_2.png) [@admin61](https://community.auth0.com/u/admin61)\
**Post date:** [December 9, 2022, 9:58am UTC](https://community.auth0.com/t/passed-audience-is-automatically-overwritten-during-authorize/96106/1 "2022-12-09T09:58:54Z")

</div>

As described here [authentication - Why is 'audience' set to 'localhost:\<port\>' with auth0? - Stack Overflow](https://stackoverflow.com/questions/55422976/why-is-audience-set-to-localhostport-with-auth0)

To receive an JWT instead of an Opaque Token I pass an Audience during /authorize. However, the Audience that I pass (explicitly) is dumped and replaced by “[https://localhost:8787](https://localhost:8787)”

Where is this coming from? Funny enough, this seems to be concated (https://…) since i dont even run TLS locally.

Also why do I have to set an audience if it is dumped anyways? Just to mention, I dont have a default audience set in my tenant.

Also, the docs state (!) " It’s recommended to use a URI but it’s not actually necessary since this is just a unique identifier."

Why is the audience the expected to be the calling host?

If I create an API with “[https://localhost:8787](https://localhost:8787)” everything works fine - but this is unexpected behaviour as far as I understand. I went 3 times through all of the docs , but did not find anything about this. Maybe someone can help

Best regards

---

<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 9, 2022, 10:20pm UTC](https://community.auth0.com/t/passed-audience-is-automatically-overwritten-during-authorize/96106/3 "2022-12-09T22:20:10Z")

</div>

Hi @admin61,

Welcome to the Auth0 Community!

> [@admin61](#):
>
> Where is this coming from?

As you’ve noted, the default setting in Auth0 is to return an opaque token.

An audience of anything else is almost certainly a result of a configuration in your tenant or is being added as part of the request from your application.

If you DM me your tenant name I can take a look at your tenant config.

> [@admin61](#):
>
> Also why do I have to set an audience if it is dumped anyways?

An access token is intended to be consumed by the audience that it was issued for. I’m not sure what you mean by dumped.

> [@admin61](#):
>
> Why is the audience the expected to be the calling host?

The _audience_ param is intended to be the consumer of the token. This is usually a backend or API in this type of setup, but could be other apps too.

---

<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 9, 2022, 10:22pm UTC](https://community.auth0.com/t/passed-audience-is-automatically-overwritten-during-authorize/96106/4 "2022-12-09T22:22:44Z")

</div>

This resource might also be helpful:

[https://community.auth0.com/t/what-is-the-audience/71414](https://community.auth0.com/t/what-is-the-audience/71414)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [January 30, 2023, 9:39pm UTC](https://community.auth0.com/t/passed-audience-is-automatically-overwritten-during-authorize/96106/5 "2023-01-30T21:39:52Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
