[Watcher] Can't edit or simulate a watch with an email action containing an authenticated reporting request

[jsanz]

This is originated from a community discussion

Kibana version:
8.10.4

Elasticsearch version:
8.10.4

Server OS version:
Elastic Cloud

Browser version:
Firefox 118

Browser OS version:
Ubuntu 20.04 LTS

Original install method:
Elastic Cloud

Describe the bug:
After creating a watcher, I can't edit it because the authentication section of an email attachment can't be parsed.

Steps to reproduce:

1. Create a watcher with an email that triggers a reporting with an authenticated request (example below)
2. Check the watcher works as expected, waiting for it or using the /_execute endpoint
3. Try to edit or simulate it in the Kibana UI

PUT _watcher/watch/test_email
{
  "trigger": {
    "schedule": {
      "interval": "1m"
    }
  },
  "input": {
    "none": {}
  },
  "condition": {
    "always": {}
  },
  "actions": {
    "email_admin": {
      "email": {
        "profile": "standard",
        "attachments": {
          "error_report.pdf": {
            "reporting": {
              "url": "URL-Generated-From-Dashrboard-Share-Pop-Up",
              "retries": 3,
              "interval": "30s",
              "auth": {
                "basic": {
                  "username": "user-here",
                  "password": "password-here"
                }
              }
            }
          }
        },
        "to": ["'My Name <my-work-email>'"],
        "subject": "Test Report"
      }
    }
  }
}

Expected behavior:
Editing and simulations work

Screenshots (if relevant):

Errors in browser console (if relevant):

I see this 400 request on a PUT to ${KIBANA_HOST}/api/watcher/watch/test_email

Any additional context:

Seems to be related (or a duplicate) to #21010

[elasticmachine]

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

[nicolam1]

This can be easily fixed by replacing ::es_redacted:: value of the password in the template with the actual password and you should be able to simulate the watcher.

[jsanz]

This can be easily fixed by replacing ::es_redacted:: value of the password in the template with the actual password and you should be able to simulate the watcher.

You are right, and since #21010 already captures the issue with redacted passwords I'm going to close this as not planned.