-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Closed
Copy link
Labels
Feature:Actions/ConnectorTypesIssues related to specific Connector Types on the Actions FrameworkIssues related to specific Connector Types on the Actions FrameworkFeature:Actions/ConnectorsManagementIssues related to Connectors Management UXIssues related to Connectors Management UXTeam:ResponseOpsPlatform ResponseOps team (formerly the Cases and Alerting teams) t//Platform ResponseOps team (formerly the Cases and Alerting teams) t//
Description
The Watcher added the following configuration, xpack.notification.email.recipient_allowlist to support only a subset of email recipients using wildcards. For example, setting xpack.notification.email.recipient_allowlist to ["*[email protected]"] will allow only recipients like [email protected] but not [email protected]. The new config is mutually exclusive with the domain_allowlist, meaning that if both are configured, Watcher will throw an error.
We should support the same functionality for Kibana alerting.
DoD
- Introduce a new
xpack.actions.email.recipient_allowlistconfiguration where users can use wildcards to put the list of allowed recipients. - Throw an error if both
xpack.actions.email.recipient_allowlistandxpack.actions.email.domain_allowlistare set on Kibana startup. - Throw an error in the email executor if the recipients (
To:,Cc:, orBcc:) are not allowed. - Show an error in the UI if someone tries to set a recipient (
To:,Cc:, orBcc:) that is not allowed. - The new setting defaults to ["*"], which means all recipients are allowed.
PR for Watcher: elastic/elasticsearch#116672
Metadata
Metadata
Assignees
Labels
Feature:Actions/ConnectorTypesIssues related to specific Connector Types on the Actions FrameworkIssues related to specific Connector Types on the Actions FrameworkFeature:Actions/ConnectorsManagementIssues related to Connectors Management UXIssues related to Connectors Management UXTeam:ResponseOpsPlatform ResponseOps team (formerly the Cases and Alerting teams) t//Platform ResponseOps team (formerly the Cases and Alerting teams) t//