From e1474e91a6a3c3e62c610015d653a533f553a5d9 Mon Sep 17 00:00:00 2001 From: Rafael Rivera Date: Thu, 4 Oct 2018 22:21:44 -0700 Subject: [PATCH] Clarify NTLMv2 support in documentation --- website/source/docs/templates/communicator.html.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/website/source/docs/templates/communicator.html.md b/website/source/docs/templates/communicator.html.md index c38e3af2f..a12fe6b3e 100644 --- a/website/source/docs/templates/communicator.html.md +++ b/website/source/docs/templates/communicator.html.md @@ -153,10 +153,12 @@ The WinRM communicator has the following options. become available. This defaults to `30m` since setting up a Windows machine generally takes a long time. -- `winrm_use_ntlm` (boolean) - If `true`, NTLM authentication will be used for WinRM, - rather than default (basic authentication), removing the requirement for basic - authentication to be enabled within the target guest. Further reading for remote - connection authentication can be found [here](https://msdn.microsoft.com/en-us/library/aa384295(v=vs.85).aspx). +- `winrm_use_ntlm` (boolean) - If `true`, NTLMv2 authentication (with + session security) will be used for WinRM, rather than + default (basic authentication), removing the requirement for basic + authentication to be enabled within the target guest. Further reading + for remote connection authentication can be found + [here](https://msdn.microsoft.com/en-us/library/aa384295(v=vs.85).aspx). - `winrm_use_ssl` (boolean) - If `true`, use HTTPS for WinRM.