When WildFly acts as a resource server and receives a bearer JWT containing an "aud" claim, it should be possible to accept multiple different pre-configured values. This use case is related specifically to the bearer-only configuration and when verify-token-audience is set to true. Currently, only client name (resource) is accepted as an audience claim.