Hi Jordan. Thanks for the information.
I tried CredSSP (and kerberos) and both give me a:
fatal: [<HOST_NAME>]: FAILED! => {
"changed": false,
"module_stderr": "#< CLIXML\r\n",
"module_stdout": "",
"msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
"rc": 1
}
I've enabled CredSSP on the agent via:
Enable-WSManCredSSP -Role Server -Force
and I am able to ping with credssp enabled:
$ ansible all -i hosts -m win_ping
<HOST_NAME> | SUCCESS => {
"changed": false,
"ping": "pong"
}
Ben
On Tuesday, November 5, 2019 at 2:48:16 AM UTC-8, Jordan Borean wrote:
>
> By default a network login on Windows does not have the users password
> available so it cannot take advantage of things that are encrypted with
> their credentials. This includes things like the Windows credential manager
> so it’s unable to find the password for your remote URL. You either need to
> connect with credssp auth or use become on the task with the users explicit
> credentials to bypass this.
>
> Thanks
>
> Jordan
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/cc5a681d-8460-4b3e-9db7-f62d1ed225f9%40googlegroups.com.
