* remove support from Windows pages, add Windows Server 2019
* jborean feedback
* Removed CBT info
Removed the CBT note about what transports Ansible actually supports. We've worked with both NTLM and Kerberos for a while now.
SSH keys are not supported when using the WinRM or PSRP connection plugins.
You cannot use SSH keys with the WinRM or PSRP connection plugins.
These connection plugins support X509 certificates for authentication instead
These connection plugins use X509 certificates for authentication instead
of the SSH key pairs that SSH supports.
of the SSH key pairs that SSH uses.
The way X509 certificates are generated and mapped to a user is different
The way X509 certificates are generated and mapped to a user is different
from the SSH implementation; consult the :ref:`windows_winrm` documentation for
from the SSH implementation; consult the :ref:`windows_winrm` documentation for
more information.
more information.
Ansible 2.8 has added experimental support for using the SSH connection plugin,
Ansible 2.8 has added an experimental option to use the SSH connection plugin,
which supports authentication with SSH keys, to connect to Windows servers. See :ref:`this question <windows_faq_ssh>`
which uses SSH keys for authentication, for Windows servers. See :ref:`this question <windows_faq_ssh>`
for more information.
for more information.
.._windows_faq_winrm:
.._windows_faq_winrm:
@ -109,9 +109,8 @@ Some ways to bypass these restrictions are to:
* Use ``win_psexec`` to run a command on the host. PSExec does not use WinRM
* Use ``win_psexec`` to run a command on the host. PSExec does not use WinRM
and so will bypass any of the restrictions.
and so will bypass any of the restrictions.
* To access network resources without any of these workarounds, an
* To access network resources without any of these workarounds, you can use
authentication option that supports credential delegation can be used. Both
CredSSP or Kerberos with credential delegation enabled.
CredSSP and Kerberos with credential delegation enabled can support this.
See :ref:`become` more info on how to use become. The limitations section at
See :ref:`become` more info on how to use become. The limitations section at
:ref:`windows_winrm` has more details around WinRM limitations.
:ref:`windows_winrm` has more details around WinRM limitations.
@ -165,7 +164,7 @@ and there is no equivalent Windows module available.
Can I connect to Windows hosts over SSH?
Can I connect to Windows hosts over SSH?
````````````````````````````````````````
````````````````````````````````````````
Ansible 2.8 has added experimental support for using the SSH connection plugin
Ansible 2.8 has added an experimental option to use the SSH connection plugin
to manage Windows hosts. To connect to Windows hosts over SSH, you must install and configure the `Win32-OpenSSH <https://github.com/PowerShell/Win32-OpenSSH>`_
to manage Windows hosts. To connect to Windows hosts over SSH, you must install and configure the `Win32-OpenSSH <https://github.com/PowerShell/Win32-OpenSSH>`_
fork that is in development with Microsoft on
fork that is in development with Microsoft on
the Windows host(s). While most of the basics should work with SSH,
the Windows host(s). While most of the basics should work with SSH,
Alicia Cozine
5 years ago
committed by