OpenSearch/x-pack/plugin/ccr/qa/security/follower-roles.yml

ccruser:
  cluster:
    - manage_ccr
  indices:
    - names: [ 'allowed-index', 'logs-eu-*' ]
      privileges:
        - monitor
        - read
        - write
        - manage_follow_index
[CCR] Make cross cluster replication work with security (#30239) If security is enabled today with ccr then the follow index api will fail with the fact that system user does not have privileges to use the shard changes api. The reason that system user is used is because the persistent tasks that keep the shards in sync runs in the background and the user that invokes the follow index api only start those background processes. I think it is better that the system user isn't used by the persistent tasks that keep shards in sync, but rather runs as the same user that invoked the follow index api and use the permissions that that user has. This is what this PR does, and this is done by keeping track of security headers inside the persistent task (similar to how rollup does this). This PR also adds a cluster ccr priviledge that allows a user to follow or unfollow an index. Finally if a user that wants to follow an index, it needs to have read and monitor privileges on the leader index and monitor and write privileges on the follow index. 2018-05-16 01:48:32 -04:00			`ccruser:`
			`cluster:`
			`- manage_ccr`
			`indices:`
[CCR] Make auto follow patterns work with security (#33501) Relates to #33007 2018-09-17 01:29:00 -04:00			`- names: [ 'allowed-index', 'logs-eu-*' ]`
[CCR] Make cross cluster replication work with security (#30239) If security is enabled today with ccr then the follow index api will fail with the fact that system user does not have privileges to use the shard changes api. The reason that system user is used is because the persistent tasks that keep the shards in sync runs in the background and the user that invokes the follow index api only start those background processes. I think it is better that the system user isn't used by the persistent tasks that keep shards in sync, but rather runs as the same user that invoked the follow index api and use the permissions that that user has. This is what this PR does, and this is done by keeping track of security headers inside the persistent task (similar to how rollup does this). This PR also adds a cluster ccr priviledge that allows a user to follow or unfollow an index. Finally if a user that wants to follow an index, it needs to have read and monitor privileges on the leader index and monitor and write privileges on the follow index. 2018-05-16 01:48:32 -04:00			`privileges:`
			`- monitor`
			`- read`
			`- write`
[CCR] Change unfollow API's privilege scheme. (#34175) Unfollow should be allowed / disallowed on a per index level instead of cluster level. Also renamed `create_follow_index` index privilege to `manage_follow_index` privilege and include unfollow and close APIs. 2018-10-06 07:38:28 -04:00			`- manage_follow_index`