# AWX Administrator - login as a different user

**URL:** <https://forum.ansible.com/t/awx-administrator-login-as-a-different-user/28154>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [July 25, 2018, 8:03pm UTC](https://forum.ansible.com/t/awx-administrator-login-as-a-different-user/28154 "2018-07-25T20:03:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ed\_perry](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@ed\_perry](https://forum.ansible.com/u/ed_perry)\
**Post date:** [July 25, 2018, 8:03pm UTC](https://forum.ansible.com/t/awx-administrator-login-as-a-different-user/28154/1 "2018-07-25T20:03:04Z")

</div>

Hey was wondering if it was possible if the AWX administrator can “BECOME” another user so I can see what they have access to, and the effect “Permissions/Orginizations/Teams” give them.

I don’t want to keep asking. “Check now” every time someone wants access to inventory/Job/… and since we are user our Corporate LDAP I can’t just change their password.

---

<div class="post-metadata">

**Author:** ![ed\_perry](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@ed\_perry](https://forum.ansible.com/u/ed_perry)\
**Post date:** [July 26, 2018, 8:22pm UTC](https://forum.ansible.com/t/awx-administrator-login-as-a-different-user/28154/2 "2018-07-26T20:22:59Z")

</div>

So should I presume no feature to test user privileges exist in AWX? And you have to login as the user?

---

<div class="post-metadata">

**Author:** ![Michael\_T\_Wiley](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@Michael\_T\_Wiley](https://forum.ansible.com/u/Michael_T_Wiley)\
**Post date:** [July 26, 2018, 8:25pm UTC](https://forum.ansible.com/t/awx-administrator-login-as-a-different-user/28154/3 "2018-07-26T20:25:04Z")

</div>

I’m not aware of anything like that besides logging in as them, but I’d probably look into revising your permissions/team/org map if this is something that’s occurring regularly.

---

<div class="post-metadata">

**Author:** ![ed\_perry](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@ed\_perry](https://forum.ansible.com/u/ed_perry)\
**Post date:** [July 26, 2018, 9:06pm UTC](https://forum.ansible.com/t/awx-administrator-login-as-a-different-user/28154/4 "2018-07-26T21:06:45Z")

</div>

Thanks, that really sucks but I get the implications of having something like that might be too risky.

Ah well Thanks for the response.

---

<div class="post-metadata">

**Author:** ![Christopher\_Meyers](https://avatars.discourse-cdn.com/v4/letter/c/3e96dc/32.png) [@Christopher\_Meyers](https://forum.ansible.com/u/Christopher_Meyers)\
**Post date:** [August 1, 2018, 4:22pm UTC](https://forum.ansible.com/t/awx-administrator-login-as-a-different-user/28154/5 "2018-08-01T16:22:41Z")

</div>

This would be an awesome feature Perry! Some design decisions would have to be flushed out. Would this sort of be an impersonation thing … or would you want a page with a list of verbs that a user can do to a list of objects? Or would you click on an object and then select the user for which you want to know what verbs that user can do? Or something else entirely?

---

<div class="post-metadata">

**Author:** ![ed\_perry](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@ed\_perry](https://forum.ansible.com/u/ed_perry)\
**Post date:** [August 1, 2018, 8:50pm UTC](https://forum.ansible.com/t/awx-administrator-login-as-a-different-user/28154/6 "2018-08-01T20:50:35Z")

</div>

The feature would be great for administration but the more I think about it. Very dangerous so auditing would have to be a lot more.

For example, as a “Administrator” I become a another user, I could then execute anything as if I were them.

So you would have to come up with: any action would be verified against a Member user but everything executed as Admin User Or you could make things read only to stop the changes from being made, or playbooks from being run.

The implementation would be simple to just allow the Admin to by pass Password Authentication of another user. After that you would have full RW as another user.

Ideally this feature should be enabled/disabled so you can Harden the system for production.
