elasticsearch/server
Michael Peterson 87211f249c
Resolve/cluster should mark remotes as not connected when a security exception is thrown (#119793) (#119866)
Fixes two bugs in _resolve/cluster.

First, the code that detects older clusters versions and does a fallback to the _resolve/index
endpoint was using an outdated string match for error detection. That has been adjusted.

Second, upon security exceptions, the _resolve/cluster endpoint was marking the clusters as connected: true,
under the assumption that all security exceptions related to cross cluster calls and remote index access were
coming from the remote cluster, but that is not always the case. Some cross-cluster security violations can
be detected on the local querying cluster after issuing the remoteClient.execute call but before the transport
layer actually sends the request remotely. So we now mark the connected status as false for all ElasticsearchSecurityException cases. End user docs have been updated with this information.
2025-01-10 01:57:36 +11:00
..
licenses Remove JNA from server dependencies (#110809) 2024-07-12 19:49:13 -07:00
src Resolve/cluster should mark remotes as not connected when a security exception is thrown (#119793) (#119866) 2025-01-10 01:57:36 +11:00
build.gradle Update Gradle wrapper to 8.12 (#118683) (#119357) 2024-12-31 08:37:28 +01:00