Ambiguous AuthorizationException

[ppf2]

Same repro steps as #4763
Except that in Step 3, the default index pattern set is another filtered alias that the user does not have access to.
As a result, the same Discover: An error occurred with your request. Reset your inputs and try again. shows up, and this time, the underlying exception from Elasticsearch Kibana cannot handle is the following:

[ppf2]

This is just a note for those who are setting up filtered aliases with Shield to work with Kibana. If you have multiple filtered aliases defined and don't want to see the above error when a user logs in who doesn't have access to the index pattern that is the default (may be another index, set of indices, or another alias), you can create an index pattern for just * and use that as the default. Note that this workaround has a performance implication. When using *, Kibana will always query all time based indices regardless of the time filter selected (this behavior will be improved when Kibana is able to use the new field stats api available in ES 2.0: #4342). The other option will be to create 1 Kibana setup per group of user (filtered alias).

[BigFunger]

The error message referred to in this issue was removed in #5176 and the system was changed to display the detailed error information from ES.