A target audience identifies the intended recipient of a token through its audience claim. API authentication uses this value to recognize tokens issued for accepted application endpoints. section 25.2 section 25.4.1
The audience must match a configured valid audience. The user-jwts tool derives valid audiences from the application URLs in launchSettings.json, so tokens can work across configured development profiles. section 25.4.1
Configured development audiences
A bearer configuration can list http://localhost:5073 and https://localhost:7112 as valid audiences. A generated JWT includes these application URLs in its aud claims. section 25.4.1
{
"Authentication": {
"Schemes": {
"Bearer": {
"ValidAudiences": [
"http://localhost:5073",
"https://localhost:7112"
],
"ValidIssuer": "dotnet-user-jwts"
}
}
}
}
Inspect a bearer authentication configuration that declares multiple valid audience URLs. section 25.4.1
