I had trouble writing to files on a NetApp device via a windows host over winrm. In the end it transpired the netapp device was not actually a 'domain peer' - it wasn't taking part in the domain and was just set up to allow 'Everyone' access to a share. That was fixed by upgrading to a newer NetApp device and I believe getting the netapp setup properly to take part in the domain. I don't recall having to set acl on the files on the NetApp though, so maybe I had a different issue. Hope this helps, Jon
On Friday, April 3, 2020 at 7:51:02 PM UTC+1, Jesse Lyon wrote: > > Hey Jordan, > > How's that different than what I'm doing here? > become: yes > become_method: runas > become_user: "[email protected] <javascript:>" > > > Should I be using a different method? > > On Friday, April 3, 2020 at 2:39:37 PM UTC-4, Jordan Borean wrote: >> >> This is because of the double hop problem, without the users credentials >> the WinRM service cannot authenticate to those fileshares as that user so >> it appears to be an anonymous user which does not have access. The only way >> around this is to use become on the task or connect with an authentication >> option that support credential delegation like CredSSP or Kerberos with >> delegation enabled. > > -- 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/acddc685-ae65-4f55-8f41-9ce6ea6b63ea%40googlegroups.com.
