Audience restriction does not match required audience – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.4-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when the audience (aud) claim in the JWT token does not match the expected audience configured in Elasticsearch. This is a security measure to ensure tokens are intended for the correct recipient. To resolve this, you can either adjust the audience in your JWT token to match the Elasticsearch configuration, or modify the Elasticsearch configuration to accept the current audience in the JWT token. Also, ensure that the JWT token is correctly formatted and encoded.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Audience restriction [{}] does not match required audience [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Audience restriction [{}] does not match required audience [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                } else {
          "Audience restriction [{}] does not match required audience [{}]"; uri; spEntityId);

            return false;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Get expert answers on Elasticsearch/OpenSearch