Hi,
I am using heartbeat 6.4.0
I am trying to monitor an https url, below is my configuration:
```auto
heartbeat.monitors:
- type: http
urls:
- https://myurl.company.com/
schedule: '@every 5m'
username: user
password: pass
```
In the kibana, I can see I am getting monitor.status as down since error.message is 401 Unauthorized
Above url asks for username and password after I load it in the browser. But the username and password option is not working or may be I am not configuring it correctly.
Can anyone guide here?
---
I curled the url and this is what I got.
```auto
curl --user "user:pass" https://myurl.company.com/
401 - Unauthorized: Access is denied due to invalid credentials.
Server Error
```
Also, I made one mistake, it is windows Authentication not basic Authentication.
---
We currently don't support NTLM authentication in heartbeat.
There have been few requests to support NTLM and other enterprise auths but not enough to include the feature request in the roadmap. A similar discussion can be found [here](https://github.com/elastic/beats/issues/22207).
If it's possible to upgrade the stack to 7.17 or better 8.2, a browser monitor (which uses Elastic Synthetics Agent) could be used to get through such authentication by writing a simple javascript. Please [see](https://www.elastic.co/guide/en/beats/heartbeat/8.2/monitor-browser-options.html).
Also worth reading the [blog post](https://www.elastic.co/blog/why-and-how-replace-end-to-end-tests-synthetic-monitors) on synthetics monitoring.
---