# Audience Server **URL:** \ **Category:** OAuth/OIDC\ **Tags:** api, spring, java\ **Created:** [September 11, 2021, 10:10am UTC](https://devforum.okta.com/t/audience-server/16075 "2021-09-11T10:10:17Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\ **Post date:** [September 14, 2021, 4:24pm UTC](https://devforum.okta.com/t/audience-server/16075/2 "2021-09-14T16:24:38Z")
The audience is the resource/server that the access token is intended for. If you are working on an OAuth/authorization use case, you will need to validate the ‘aud’ claim in the token to ensure that the token that was received is intended to be used by the accessed resource. More details about the Audience claim is in the JWT RFC: [rfc7519](https://datatracker.ietf.org/doc/html/rfc7519#section-4.1.3) If you are using the Org Authorization server ([https://org.okta.com/oauth2/v1/authorize](https://org.okta.com/oauth2/v1/authorize), etc), the audience will be the client\_id. If you are using a Custom Authorization Server ([https://org.okta.com/oauth2/authorizationServerId/v1/authorize](https://org.okta.com/oauth2/authorizationServerId/v1/authorize), etc), you will [set this value yourself when you create the server](https://developer.okta.com/docs/guides/customize-authz-server/create-authz-server/) and it should be the absolute path for the protected resource, e.g. [https://api.example.com/pets](https://api.example.com/pets). --- _[View the full topic](https://devforum.okta.com/t/audience-server/16075)._