# How to use pbrun\_exe in 1.9+

**URL:** <https://forum.ansible.com/t/how-to-use-pbrun-exe-in-1-9/18104>\
**Category:** Ansible Project\
**Created:** [April 28, 2015, 2:17pm UTC](https://forum.ansible.com/t/how-to-use-pbrun-exe-in-1-9/18104 "2015-04-28T14:17:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wim\_Van\_Dijck](https://avatars.discourse-cdn.com/v4/letter/w/e9a140/32.png) [@Wim\_Van\_Dijck](https://forum.ansible.com/u/Wim_Van_Dijck)\
**Post date:** [April 28, 2015, 2:17pm UTC](https://forum.ansible.com/t/how-to-use-pbrun-exe-in-1-9/18104/1 "2015-04-28T14:17:34Z")

</div>

Hi,

running ansible 2.0.0 from git repo.  
I’m very excited to try out the new become feature with powerbroker, but I’m struggling to get it to work with our setup.  
I do realize this feature is still alpha btw 😉

I read that there is a setting ''pbrun\_exe", just like su\_exe, but I cannot get it to work.  
I would like to try it, since our powerbroker profiles are very strict and pbrun can run very few commands.  
However, for installation purposes we can get root elevation, so pbrun su root is allowed.  
So I would basically like to run all commands that way.

This works fine for adhoc commands btw, if I use su\_exe = pbrun su root, then I can run single commands and even modules.  
But for playbooks this doesn’t seem to work.

Any pointers on how I can get this to work?

Kind regards,  
Wim

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [April 28, 2015, 3:48pm UTC](https://forum.ansible.com/t/how-to-use-pbrun-exe-in-1-9/18104/2 "2015-04-28T15:48:33Z")

</div>

ansible does not support chaining privilege escalation methods and  
requires permissive access to run commands as a user  
[http://docs.ansible.com/become.html](http://docs.ansible.com/become.html) (read notes)