# Windows authentication

**URL:** <https://forum.ansible.com/t/windows-authentication/21120>\
**Category:** Ansible Project\
**Tags:** windows, aws\
**Created:** [April 10, 2016, 6:32pm UTC](https://forum.ansible.com/t/windows-authentication/21120 "2016-04-10T18:32:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anjana\_Raghavendra\_P](https://avatars.discourse-cdn.com/v4/letter/a/d9b06d/32.png) [@Anjana\_Raghavendra\_P](https://forum.ansible.com/u/Anjana_Raghavendra_P)\
**Post date:** [April 10, 2016, 6:32pm UTC](https://forum.ansible.com/t/windows-authentication/21120/1 "2016-04-10T18:32:07Z")

</div>

Hi,

We are using CIS hardened AWS windows AMI in our production servers. What this means is the winrm basic authentication is disabled at client and service level. Now, I am unable to use the ansible to configure/deploy this server. Can anyone help me in this?  
I have searched through several sites but didn’t come across anyone who is having the same issue. So, porting this question here.

Thanks,  
Raghavendra.

---

<div class="post-metadata">

**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\
**Post date:** [April 12, 2016, 1:30pm UTC](https://forum.ansible.com/t/windows-authentication/21120/2 "2016-04-12T13:30:48Z")

</div>

Hi,

Perhaps you can use User Data feature of AWS to achieve this. Might be worth reading this if you have not seen it already: [https://www.ansible.com/blog/easily-provision-windows](https://www.ansible.com/blog/easily-provision-windows)

Jon

---

<div class="post-metadata">

**Author:** ![Matt\_Davis](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@Matt\_Davis](https://forum.ansible.com/u/Matt_Davis)\
**Post date:** [April 12, 2016, 4:02pm UTC](https://forum.ansible.com/t/windows-authentication/21120/3 "2016-04-12T16:02:13Z")

</div>

Ansible 2.1 is scheduled to ship with NTLM authentication support (when paired with an updated version of pywnirm)- this _should_ work on a CIS-hardened image correctly. There are coordinated changes we’ve been making to a number of upstream projects (pywinrm, requests\_ntlm, requests\_kerberos) that need to be in place for this support to “light up”, but hopefully all will be released around the same time (unfortunately, mostly outside our control).

I’m assuming you’re using something like this? [https://aws.amazon.com/marketplace/pp/B00UVT62LG/ref=sp\_mpg\_product\_title/189-1125211-0773662?ie=UTF8&sr=0-8](https://aws.amazon.com/marketplace/pp/B00UVT62LG/ref=sp_mpg_product_title/189-1125211-0773662?ie=UTF8&sr=0-8) - I’ll try to test the NTLM support on that image to ensure that it works properly out of the box.

Keep an eye out for the release of Ansible 2.1 and on our Windows guide page at [http://docs.ansible.com/ansible/intro\_windows.html](http://docs.ansible.com/ansible/intro_windows.html) - we’ll update the documentation there on how to use NTLM once all the required upstream project updates are publicly released. Should be a matter of weeks, but can’t give a more concrete date than that right now.

-Matt Davis  
Principal Software Engineer, Ansible Core (Windows)