[Actions] ensure built-in email action works with cloud smtp relay

[pmuellr]

Our current built-in email action has only been tested with mail "services" (like the nodemailer built-in "gmail" service). For cloud, sounds like every cluster will have an smtp relay available.

We should make sure we can actually use this relay successfully, using the built-in email. We may need to provide some additional functionality to make it work.

[elasticmachine]

Pinging @elastic/kibana-stack-services (Team:Stack Services)

[pmuellr]

This should be easy to test once #50209 lands - "Enable alerting plugins by default". Spin up a cloud instance using Kibana master, and try creating an email action with the existing email action type, and then executing it.

[peterschretlen]

I tried this out today and it looks like we have a similar problem to #55359. The email action requires a user and password but the internal service does not have authentication, and fails because we're trying to give it credentials:

$ curl -s -k -Hkbn-xsrf:true -u elastic:########## -HContent-Type:application/json -d '{"name":"relay", "actionTypeId":".email", "config":{"host":"########## ", "port": #######, "secure":true, "from":"noreply@kibanaalert.found.io" }, "secrets": {"user":"x", "password":"x"} }' https://######################.europe-west1.gcp.cloud.es.io:9243/api/action | jq .
{
  "id": "beda7d95-ad21-4900-880d-12ea326d25ae",
  "actionTypeId": ".email",
  "name": "relay",
  "config": {
    "host": "###############",
    "port": #########,
    "secure": true,
    "from": "noreply@kibanaalert.found.io",
    "service": null
  }
}

$ curl -s -k -Hkbn-xsrf:true -u elastic:########## -HContent-Type:application/json -d '{ "params":{"to":["##########@elastic.co"],"subject":"test email","message":"this is a test"} }' https://######################.europe-west1.gcp.cloud.es.io:9243/api/action/beda7d95-ad21-4900-880d-12ea326d25ae/_execute | jq .
{
  "status": "error",
  "actionId": "beda7d95-ad21-4900-880d-12ea326d25ae",
  "message": "error sending email",
  "serviceMessage": "Invalid login: 503 5.5.1 Error: authentication not enabled"
}

[pmuellr]

Not sure what the remediation is here? Not require auth credentials and pass those to node mailer? I think I need more context ...

nvm - think I understand - seems like the fix for #57143 will fix this

[pmuellr]

I believe this was fixed for 7.7 or a patch of that, but would be good to re-test with 7.8 manually to make sure things are still working, since we don't have an automated test for this.

[ymao1]

Closing as done.

[pmuellr]

We've tested this numerous times over multiple releases - should work now in recent Kibanas.