# Watcher reporting basic auth not working, password not saved **URL:** \ **Category:** Elasticsearch\ **Created:** [November 21, 2017, 5:07pm UTC](https://discuss.elastic.co/t/watcher-reporting-basic-auth-not-working-password-not-saved/108597 "2017-11-21T17:07:56Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Cre8ivE\_OnE](https://avatars.discourse-cdn.com/v4/letter/c/4bbf92/32.png) [@Cre8ivE\_OnE](https://discuss.elastic.co/u/Cre8ivE_OnE)\ **Post date:** [November 21, 2017, 6:04pm UTC](https://discuss.elastic.co/t/watcher-reporting-basic-auth-not-working-password-not-saved/108597/7 "2017-11-21T18:04:04Z")
Experiencing similar issue (we opened a similar ticket _on v5.6.3_ about 19m after this one was opened - crazy!) - watching both threads for a solution... Simulating the watcher, before saving it, seems to trigger fine Once I SAVE the JSON definition, the "password" element in the JSON is parsed out by the Kibana server as it is performing the save action. Re-opening the watch and attempting to simulate then produces the error: Watcher: [parse\_exception] password is a required option This seems to be a **"feature"** as reported here : > [@Password field gets deleted after adding a watch](https://discuss.elastic.co/t/password-field-gets-deleted-after-adding-a-watch/88178): > > Hello, I've been trying to add a new watcher that will email a report to multiple users, however after I've added the watch (either via web UI or curl) and try to run it, I get the following error "password is a required option". Looking at the watch after I've inserted it I noticed the password filed is gone (under email attachment). I've also tried to edit the watch via web UI after adding it, and after I hit 'save' the password is gone again. Here is my watch: { "trigger" : { "schedule"… So... irritating messaging? Is there anyway to get a different, more explicit, message 🙂 --- _[View the full topic](https://discuss.elastic.co/t/watcher-reporting-basic-auth-not-working-password-not-saved/108597)._