# local\_action user

**URL:** <https://forum.ansible.com/t/local-action-user/11898>\
**Category:** Ansible Project\
**Created:** [September 16, 2012, 4:53am UTC](https://forum.ansible.com/t/local-action-user/11898 "2012-09-16T04:53:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonathan\_Palley](https://avatars.discourse-cdn.com/v4/letter/j/dc4da7/32.png) [@Jonathan\_Palley](https://forum.ansible.com/u/Jonathan_Palley)\
**Post date:** [September 16, 2012, 4:53am UTC](https://forum.ansible.com/t/local-action-user/11898/1 "2012-09-16T04:53:01Z")

</div>

> From my understanding/testing the local\_action connects to 127.0.0.1 using the current playbooks user.

I’m trying to understand this. In my case, I’ve got a user on my system that I’m running ansible-playbooks from and then I’ve got various users depending upon the app on my servers. I want to setup a localhost trigger using the local\_action. Right now, however, the local\_action attempts the localhost login using the playbook’s user - which I don’t necessarily have a reason to exist on my ansible system.

Is there a reason for this? Would there be support for changing this to use the user that ansible is executed from? Am I missing something?

JP

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [September 16, 2012, 3:20pm UTC](https://forum.ansible.com/t/local-action-user/11898/2 "2012-09-16T15:20:40Z")

</div>

It seems reasonable (and cleanest) to make local\_action imply "-c  
local" for just that task and not just "delegate\_to: 127.0.0.1".

Patches would be accepted.