diff options
author | Tegan Snyder <tsnyder@tegdesign.com> | 2016-04-25 10:24:26 -0500 |
---|---|---|
committer | Brian Coca <bcoca@ansible.com> | 2016-04-25 11:24:26 -0400 |
commit | bf0da4aa3c0417551c9163f13ed05dc5d70322ab (patch) | |
tree | ccf86d77c8712894edcff2cea136cc581b544c5f /docsite | |
parent | 2424d57868220263566e5993bced9012d59fc589 (diff) | |
download | ansible-bf0da4aa3c0417551c9163f13ed05dc5d70322ab.tar.gz |
add centrify dzdo escalation (#15219)
add dzdo context, and test
Diffstat (limited to 'docsite')
-rw-r--r-- | docsite/rst/become.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docsite/rst/become.rst b/docsite/rst/become.rst index e72e40c719..9d962174cf 100644 --- a/docsite/rst/become.rst +++ b/docsite/rst/become.rst @@ -8,12 +8,12 @@ Ansible can use existing privilege escalation systems to allow a user to execute Become `````` Ansible allows you 'become' another user, different from the user that logged into the machine (remote user). This is done using existing -privilege escalation tools, which you probably already use or have configured, like 'sudo', 'su', 'pfexec', 'doas', 'pbrun' and others. +privilege escalation tools, which you probably already use or have configured, like 'sudo', 'su', 'pfexec', 'doas', 'pbrun', 'dzdo', and others. .. note:: Before 1.9 Ansible mostly allowed the use of `sudo` and a limited use of `su` to allow a login/remote user to become a different user and execute tasks, create resources with the 2nd user's permissions. As of 1.9 `become` supersedes the old sudo/su, while still being backwards compatible. - This new system also makes it easier to add other privilege escalation tools like `pbrun` (Powerbroker), `pfexec` and others. + This new system also makes it easier to add other privilege escalation tools like `pbrun` (Powerbroker), `pfexec`, `dzdo` (Centrify), and others. .. note:: Setting any var or directive makes no implications on the values of the other related directives, i.e. setting become_user does not set become. @@ -29,7 +29,7 @@ become_user set to user with desired privileges, the user you 'become', NOT the user you login as. Does NOT imply `become: yes`, to allow it to be set at host level. become_method - at play or task level overrides the default method set in ansible.cfg, set to 'sudo'/'su'/'pbrun'/'pfexec'/'doas' + at play or task level overrides the default method set in ansible.cfg, set to 'sudo'/'su'/'pbrun'/'pfexec'/'doas'/'dzdo' Connection variables @@ -60,7 +60,7 @@ New command line options --become-method=BECOME_METHOD privilege escalation method to use (default=sudo), - valid choices: [ sudo | su | pbrun | pfexec | doas ] + valid choices: [ sudo | su | pbrun | pfexec | doas | dzdo ] --become-user=BECOME_USER run operations as this user (default=root), does not imply --become/-b |