Tim Vernum 463133b7de [Security] Cross cluster wildcard security (elastic/x-pack-elasticsearch#1290) ...

Support the resolution of remote index names, including those that contain wildcards in the cluster name or index part)

Specifically these work:
- `GET /remote*:foo/_search`
- `GET /*:foo/_search`
- `GET /*:foo,*/_search`
- `GET /remote:*/_search`
- `GET /*:*/_search`

This change assumes that every user is allowed to attempt a cross-cluster search against any remote index, and the actual authorisation of indices happens on the remote nodes. Thus ` GET /*:foo/_search` will expand to search the `foo` index on every registered remote without consideration of the roles and privileges that the user has on the source cluster.

Original commit: elastic/x-pack-elasticsearch@b45041aaa3

2017-05-15 15:02:13 +10:00

..

bin/x-pack

Rename core plugin and transport dirs

2017-02-10 11:02:42 -08:00

bwc-zip

Build: Build 5.x version of xpack for bwc tests to use (elastic/x-pack-elasticsearch#885)

2017-04-07 22:19:30 -07:00

config/x-pack

Rename core plugin and transport dirs

2017-02-10 11:02:42 -08:00

keys

Rename core plugin and transport dirs

2017-02-10 11:02:42 -08:00

licenses

Update Netty to 4.1.11.Final

2017-05-12 15:54:05 -04:00

src

[Security] Cross cluster wildcard security (elastic/x-pack-elasticsearch#1290)

2017-05-15 15:02:13 +10:00

build.gradle

Adapt x-pack after the parent/child modularisation (elastic/x-pack-elasticsearch#1407)

2017-05-12 15:59:40 +02:00