# Reindex with authorization on remote

**URL:** <https://discuss.elastic.co/t/reindex-with-authorization-on-remote/155070>\
**Category:** Elasticsearch\
**Created:** [November 1, 2018, 7:35pm UTC](https://discuss.elastic.co/t/reindex-with-authorization-on-remote/155070 "2018-11-01T19:35:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![shradhatx](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shradhatx/32/45398_2.png) [@shradhatx](https://discuss.elastic.co/u/shradhatx)\
**Post date:** [November 1, 2018, 7:35pm UTC](https://discuss.elastic.co/t/reindex-with-authorization-on-remote/155070/1 "2018-11-01T19:35:58Z")

</div>

I am trying to test ES upgrade from 2.2 to 6.4 on windows. The remote requires NTLM authorization. I am passing username and password but looks like it takes basic auth. In ES log I am seeing "NEGOTIATE authentication\_error: Credentials cannot be used for NTLM authentication". How do I change the authentication type to NTLM from basic auth in \_reindex body? This is what I am providing in postman-

POST /\_reindex  
{"source": {"remote": {"host": "http//...:, "username: "myuser", "passowrd": "mypasswd", "domain": "mydomain"}, "index": "myremoteindex"}, "dest" {"index": "mylocalindex"}}

---

<div class="post-metadata">

**Author:** ![s1monw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s1monw/32/3637_2.png) [@s1monw](https://discuss.elastic.co/u/s1monw)\
**Post date:** [November 9, 2018, 9:09am UTC](https://discuss.elastic.co/t/reindex-with-authorization-on-remote/155070/2 "2018-11-09T09:09:00Z")

</div>

I don't think that is supported. @nik9000 ideas?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 7, 2018, 9:09am UTC](https://discuss.elastic.co/t/reindex-with-authorization-on-remote/155070/3 "2018-12-07T09:09:05Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.