Skip to content

Commit b125fb2

Browse files
committed
add readme note about alerting / manage_api_key cluster privilege
resolves #54525
1 parent e90ca93 commit b125fb2

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

x-pack/legacy/plugins/alerting/README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,14 @@ When security is enabled, an SSL connection to Elasticsearch is required in orde
3232

3333
When security is enabled, users who create alerts will need the `manage_api_key` cluster privilege. There is currently work in progress to remove this requirement.
3434

35+
Note that the `manage_own_api_key` cluster privilege is not enough - it can be used to create API keys, but not invalidate them, and the alerting plugin currently both creates and invalidates APIs keys as part of it's processing. When using only the `manage_own_api_key` privilege, you will see the following message logged in the server when the alerting plugin attempts to invalidate an API key:
36+
37+
```
38+
[error][alerting][plugins] Failed to invalidate API Key: [security_exception] \
39+
action [cluster:admin/xpack/security/api_key/invalidate] \
40+
is unauthorized for user [user-name-here]
41+
```
42+
3543
## Alert types
3644

3745
### Methods

0 commit comments

Comments
 (0)